PlugsightDocs

Support teams

Connect Zendesk and your support inboxes so your AI can find ticket history, spot trends and draft replies that you approve.

Who it's for

You answer customers in Zendesk, a shared support inbox, or both. You need the full history before you reply, you want to know what customers are raising this week, and you write many similar replies.

With Plugsight, your AI searches and reads tickets and emails, counts tickets for any period, and drafts replies and internal notes. Nothing goes to a customer without your approval in the chat.

Reading Zendesk and email works on every plan. Replies, notes, ticket updates, macros and sending email need Pro or Agency.

Connectors to set up

Connector What it adds
Zendesk Search tickets with Zendesk search syntax, read full conversations including internal notes, find users, ticket counts, macros; with your approval: replies, internal notes, ticket updates, new tickets and macros
Your support mailbox, for example Gmail, Outlook or another provider Search and read customer emails and attachments, draft replies; with your approval: send, archive, label and mark
Mailchimp Optional: check whether a customer is subscribed, and when they joined
WooCommerce or Magento Optional: look up a customer's orders while you answer them

Connect Zendesk with your own agent or admin login. Zendesk then applies your agent's permissions to everything your AI does, and records replies and changes under your name.

  • Name: "Support"
  • Account access: Selected accounts: your Zendesk, the support mailbox, and the store if you connected one. Leave personal mailboxes out.
  • Allow changes: ticked, so your AI can reply and update tickets after your approval.

Then, on Connections, decide each account's switch:

Account Start with Turn on when
Zendesk Read-only You're happy with the notes and drafts your AI writes. The switch then shows Can reply & update.
Support mailbox Drafts only You want your AI to send approved replies itself. The switch then shows Can send.

If a team lead only needs to look at trends, give them a server with Allow changes unticked. See Use several MCP servers.

Example questions

  • "What are the top five reasons for tickets this week?"
  • "Which urgent tickets have had no reply for more than a day?"
  • "Summarise everything this customer has raised in the last 90 days, in Zendesk and by email."
  • "Find tickets tagged 'refund' that are still open."
  • "How many tickets did we solve last week compared with the week before?"
  • "How many tickets are new, open, pending and on hold in the Billing group right now?"
  • "Draft an internal note on ticket 4821 summarising the issue and what we've tried."
  • "Draft a reply to ticket 4821 using our refund policy email."
  • "Which macros do we have for shipping delays? Preview what 'Delay apology' would do to ticket 4821."
  • "Set ticket 4821 to pending, assign it to Sam and add the tag 'carrier-issue'."
  • "Summarise this week's customer enquiries in the support inbox and draft replies to the three oldest."
  • "What did the PDF attached to the customer's last email say about the damage?"

A typical week

Monday: the queue. Ask for ticket counts (new, open, pending, on hold, unsolved) and the urgent tickets with no reply. Ask for the top reasons for tickets created over the weekend.

Every day: first replies. For each ticket you pick up, ask your AI for the customer's history and a draft reply or note. Read it, edit it in the chat, then approve it. With macros, your AI previews exactly what the macro changes before you say yes.

Wednesday: follow-ups. Ask for pending tickets that haven't been updated in a few days, and for support emails you haven't answered.

Friday: trends. Compare tickets created and solved this week against last week, and ask what customers raised most. Share the summary with your team or product manager.

Safety tips

  • Approve every customer-facing message. Your AI shows you the reply, the ticket and any status change before it acts. Plugsight refuses changes the AI hasn't marked as approved. See Approvals in the chat.
  • Prefer internal notes while you build trust. Notes are seen only by agents. A new ticket's first message is an internal note by default, so the customer isn't emailed unless you ask.
  • Keep the email limit sensible. Your AI can send at most the daily email limit from each mailbox in 24 hours (20 by default).
  • Pause in a hurry. If a reply goes out that shouldn't have, or someone else is using your chat, click Pause on the Helpdesk or Email row on Permissions, or Pause everything. Your AI keeps reading. See Pause changes.
  • Review Activity. Every reply, note and update is listed, with blocked attempts and their reasons. See Activity log.