> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/ask-ziggy.md). # Ask Ziggy Ask Ziggy™ is a chat panel inside the Zigpoll dashboard. It knows which page you are on, can read your surveys and responses, and can propose changes — a new survey, an extra question, a Spanish translation, a targeting rule — that you review and apply with one click. Nothing is saved until you approve it. It is available on every plan and to every team member. ## Opening the panel Click the sparkles icon in the top-right of the dashboard, next to Help, or press **⌘ .** (Ctrl+. on Windows) from any page. The same shortcut closes it. The panel remembers whether you left it open. New accounts also see **Not sure where to get started? Ask Ziggy** at the bottom of the onboarding checklist. The chip under the panel header shows what Ziggy is looking at — for example *Account › Post-Purchase Survey › How did you hear about us? › Question editor*. Move to a different page and the context follows you. ## What you can ask **Questions about Zigpoll.** Ziggy searches this documentation before answering "how does X work" questions and links the page it used. > Why isn't this survey showing on my thank-you page? > > What is the difference between a survey link and a public link? **Questions about your account.** Plan, renewal, response limits, connected integrations, team size, language and consent settings. > What plan am I on and how many responses do I have left this month? **Questions about your data.** Ziggy can read responses, summaries, verbatims, trends, drop-off, participant and Shopify order data, and compare surveys. > What are the top three reasons people gave for almost not buying? > > Compare response rates across my surveys this month. **Changes.** Describe what you want and Ziggy proposes it. > Build a post-purchase "how did you hear about us" survey. > > Add an NPS question at the end of this survey. > > Translate this survey into Spanish. > > Only show this survey to orders shipping to Canada. **Getting around.** Ziggy can open dashboard pages by name and open a few dialogs directly. > Take me to Integrations. > > Show me the QR code for this survey. > > Export these responses to CSV. > > Delete this participant's test responses. When the thread is empty, four **Try asking** suggestions appear. They are picked for the page you are on and for where your account is — a brand-new account gets prompts about creating and installing a first survey, an account with lots of responses gets prompts about analysis. ## Reviewing and applying changes Every change Ziggy wants to make arrives as a **proposal card** with a one-line summary, a **Details** toggle that shows exactly what will be written, and **Apply** and **Discard** buttons. If a single request produces several changes — a new survey and its five questions, say — a bar underneath offers **Apply All** and **Discard All**. Proposals appear once Ziggy has finished the turn, so you always review the complete set. After you apply a change, the dashboard opens the form it landed in: a new survey opens on its Questions tab, an edited question opens in the editor, a translation opens the Language tab, a webhook opens Integrations. Check the result there. {% hint style="warning" %} **Applied changes are permanent.** There is no undo. Proposals that overwrite or send something — editing or reordering questions, replacing translations, changing action rules, sending an email or SMS invitation, deleting a webhook — are marked **This can't be undone** while they wait for your decision. Read the Details before applying those. {% endhint %} ### Editing the question you have open If you are in the question editor and ask for a wording change — *shorten this*, *add an "Other" option with a text box* — Ziggy proposes it against the **unsaved draft** on your screen rather than the saved question. Applying fills the form; you still click **Save**, so you can adjust before anything is stored. ### What runs without a proposal Two things happen immediately when Ziggy decides to do them, because they change nothing in your account: opening a dashboard page, and opening a dialog (CSV export, QR code, share link, invite a team member, Contact Us, the Reset Survey Data confirmation, or the Delete Responses checkboxes on a participant's page). The QR code and share link dialogs only exist once a survey is live, and Reset Survey Data only while the survey is under 48 hours old. Deleting still needs your confirmation in the dialog Ziggy opened. ## What Ziggy can change | Area | Examples | | ------------------ | -------------------------------------------------------------------------------------------------------- | | Surveys | Create, duplicate and publish surveys; change delivery, targeting, timing, frequency and design settings | | Questions | Add, edit, retype and reorder questions, including logic and branching; commit staged changes | | Languages | Write translations for one language at a time; existing languages are merged, not replaced | | Action rules | Add or remove survey actions such as Shopify tags, Klaviyo events, redirects and webhook triggers | | Links | Generate a trackable survey link | | Invitations | Send an email or SMS survey invitation — only when you explicitly ask to send | | Synthetic research | Start or cancel a research run | | Webhooks | Create a signed webhook or delete one (account admins only) | Every proposal is validated before it is shown to you — a multiple-choice question with no answers, a matrix with one column, or a redirect with no URL is sent back to Ziggy to fix rather than offered to you. ## Team roles Ziggy respects the role of whoever is signed in. See [Adding Team Members](/tutorials/adding-team-members.md) for how roles are assigned. | Role | What Ziggy does | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Owner, Admin, Billing admin | Everything above, including webhooks | | Editor | Everything except creating or deleting webhooks | | Read only (Analyst) | Answers questions and analyzes data. Cannot propose changes, open pages or open dialogs; it explains what to do instead | A change a role is not allowed to make is never proposed. If one slips through — for example a thread started by an admin and continued by an editor — the card reads *Your role doesn't allow this change. Ask an account admin.* ## Reaching a person If Ziggy cannot find an answer, thinks you have hit a bug, or the request is something only the Zigpoll team can do (billing corrections, account changes), it says so and opens the **Contact Us** form with your details filled in. You can also just ask: *how do I reach support?* ## Usage and limits * Each message you send uses one **insight credit**, from the same monthly pool as the Insights page. Applying a proposal does not use a credit. Credit allotments per plan are listed in [Subscription Plans](/subscription-plans.md). A running balance appears in the panel when you are close to the limit. * Long requests are capped at ten tool steps per message. If Ziggy runs out it tells you and you can ask it to continue. * Press **Stop** to cancel a reply in progress. * The conversation lasts for your session and is kept as you move between pages. It is cleared when you reload the browser or click the refresh icon in the panel header. * From inside a survey, Ziggy focuses on that survey. For account-wide questions — *compare all my surveys* — ask from the account dashboard. ## Privacy Ziggy is powered by an OpenAI model. Requests are sent with retention disabled, so nothing about your account or your customers is stored by OpenAI or used for training. With each message Ziggy receives your question, the earlier turns of the conversation, what page you are on (including the unsaved contents of a question you are editing), and a summary of your account: store name and websites, plan and limits, responses used this month, language, currency, domains, which integrations are connected, and team size by role. Integration credentials, API keys, and team members' email addresses are never sent. Survey responses are read only when your question needs them, through the same tools available in the [MCP server](/integrations/mcp.md). Each request is authenticated with a short-lived key that is deleted when the reply finishes. ## Related * [Analytics, AI, and Reporting](/analytics-ai-and-reporting.md) — Z-GPT Insights and the Insights-page chat for deep analysis of a single survey * [MCP server](/integrations/mcp.md) — the same tools Ziggy uses, from Claude, ChatGPT, Perplexity and other assistants * [Web API](/web-api.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zigpoll.com/ask-ziggy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.