Getting started
Add a web form or the API
Besides email, tickets can arrive from a hosted web form, from your own website or systems through the intake API, or be logged by hand for phone calls and walk-ups. Each ticket records its channel so reporting can split by source.
5 steps · 4 min read
Before you start
- Admin access for the form and API keys. Anyone on the team can log a manual ticket.
- 1
Switch on the hosted form
Settings → API → Hosted form. Turn it on and share the link, or embed it on your own site. No coding needed.
You’ll see: Submissions appear as tickets with the Web form channel. At the monthly ticket limit they are kept and become tickets when there is room.
- 2
Create an API key
Settings → API → API keys. Create a key, copy it once, and keep it with your other secrets. Keys can be revoked at any time; creating and revoking are both audited.
- 3
Send a ticket from your code
The same page has the API reference and copy-ready code for Node.js, Python, PHP, Ruby and Go. Requests are rate-limited, and a repeat submission sent with the same idempotency key is safely ignored.
- 4
Mark signed-in customers, if you can
A "Report a problem" button inside your product can tell QueuePower the customer is signed in. Full AI can then reply from the first message. Your workspace is responsible for that claim.
- 5
Log calls and walk-ups by hand
Use the New ticket button on the Tickets page. The AI reads a manual ticket exactly like an email.
Good to know
- Form and API tickets count as verified as soon as the customer replies by email. Until then Full AI sends a standard acknowledgement and a person replies.
Related guides
- Connect your support mailboxKeep support@yourcompany.com. QueuePower reads it, and replies come from the same address.Read
- Slack and Teams alertsNew tickets posted where the team already talks, and a nudge when nobody is on duty.Read
- Supervised to Full AI, category by categoryThe evidence that a category is ready, what Full AI will and won't send, and how to switch it on.Read