- Docs
- Guides
WHMCS ticket sync: tickets both ways
Ticket sync connects the tickets in your WHMCS with the tickets in TalkingDot. A ticket opened in WHMCS shows in your inbox, a ticket opened here shows in WHMCS, and every reply, private note and status change is copied to the other side. Your team answers from whichever screen it prefers, and a customer never gets the same reply twice.
What syncs
- New tickets, both ways. Each WHMCS ticket in a synced department has one TalkingDot ticket, and the other way round.
- Replies from the customer and from your team, including replies by email to either side.
- Private notes. Notes in TalkingDot become WHMCS ticket notes, and WHMCS notes become notes here, marked with who wrote them. Customers never see them.
- Status and priority. See Statuses. Low, Medium and High in WHMCS are Low, Normal and High here; Urgent here is High in WHMCS.
- Department. Each WHMCS department is a ticket type here, and can go to a team. See Departments and ticket types.
- Who handles it. The admin a ticket is flagged to in WHMCS is the assignee here, when their email matches a teammate, and the other way round.
- Files, within each side’s limits. See Files.
Not synced in this version: custom ticket fields, CC addresses, the related service or domain, tags, and edits to a reply after it was sent. Chats that are not tickets stay in TalkingDot; once you make one a ticket, the rules below apply.
Before you start
- Ticket sync is on Starter, Pro, Lifetime and Reseller accounts. On other plans you keep the WHMCS customer card next to every chat.
- Your WHMCS is connected, runs WHMCS 8.0 or newer, and has the TalkingDot module 1.3.0 or newer. Customer details keep working on WHMCS 7.10 and older modules.
- Ticket sync isn’t available for Help & support workspaces yet.
Set it up
- Update the module. In TalkingDot open Settings → Integrations → WHMCS, click Download WHMCS module and upload it over the old one. If you upload by FTP, clear PHP’s cache afterwards (restart PHP-FPM, or ask your host to): until then WHMCS can keep running the old files, and the settings page tells you so.
- Check the WHMCS switch. In WHMCS, Configuration → System Settings → Addon Modules → TalkingDot Live Chat → Configure has Allow ticket sync. It is on by default, and switching it off stops ticket sync from the WHMCS side at any time.
- Click Set up ticket sync in the Ticket sync card. We read your departments, ticket statuses and admins from WHMCS.
- Check the choices: a ticket type (and team) for each department, the department for tickets opened here, who emails customers, and the admin that replies from teammates who aren’t WHMCS admins are posted as.
- Click Start syncing. Your open WHMCS tickets come in with their conversations, and from then on new tickets and replies sync both ways.
The first import brings in open tickets only; closed ones stay in WHMCS. Each ticket comes in with up to its last 500 messages, and a note points to WHMCS for older ones. Nobody gets an email, no automation runs, and the messages keep their WHMCS dates. Your existing TalkingDot tickets are not sent to WHMCS. If tickets are off in your workspace, starting sync turns them on.
Tickets opened here
- By themselves: a new ticket goes to WHMCS and opens in the customer’s WHMCS account only when their email is proven on both sides. Here: they signed in on your site, confirmed a code or support PIN, wrote from an authenticated email address, or came from an import or the API. In WHMCS: the address is the main email of a client or of a user who signs in, and WHMCS has verified it. If your WHMCS doesn’t verify email addresses, no ticket goes by itself.
- With one click: when the address matches a WHMCS client but isn’t proven like that (WHMCS hasn’t verified it, it is a contact added to a client’s account, or a teammate typed it in here), the ticket’s Ticket panel says so and offers Send to WHMCS as … with the client’s name. Click it only when you’re sure it’s them: any client can add any address as a contact, and anyone can type any address in a chat.
- As a guest ticket: for anyone else, or when you aren’t sure, click Send to WHMCS in the Ticket panel (or in ⋯), or Send as a guest ticket next to the warning. It opens in WHMCS as a guest ticket with the customer’s name and email. Only the Send to WHMCS as … button itself opens a ticket in that client’s account.
- If the customer already got the “ticket created” email from TalkingDot, the ticket opens in WHMCS without WHMCS’s own “ticket opened” email, so they don’t get two. The Ticket panel says so before you send it.
- A chat you make into a ticket goes to WHMCS with the chat so far (the last 50 messages the customer saw) as its first message. Private notes are never sent as the opening message; your notes from before stay here.
- Tickets from before you switched sync on can be sent the same way, by hand.
- If a send fails, the ticket shows Not sent to WHMCS with the reason, an Error ID and Retry. Cancel sending to WHMCS in ⋯ keeps it here only.
Who emails customers
A customer never gets the same reply twice. You choose in the settings which side sends the ticket emails:
| Choice | What the customer gets |
|---|---|
| WHMCS sends its usual emails (recommended) | WHMCS’s “ticket opened” and reply emails with the link to your client area, also for replies written in TalkingDot. TalkingDot sends nothing about these tickets, except for tickets that started as a chat (see below). Email replies go to WHMCS and come over by themselves. |
| TalkingDot sends the emails | TalkingDot’s ticket emails with its usual rules, also for replies written in WHMCS. WHMCS still sends its own confirmation when a ticket is opened in WHMCS. For synced tickets WHMCS doesn’t send its “ticket auto-closed” notice or its feedback request: the ticket closes here too, and the “ticket closed” email from TalkingDot covers it, so the customer gets one closing email. If TalkingDot can’t take a reply written in WHMCS at that moment, WHMCS emails that reply itself (at the latest 15 minutes later) and TalkingDot doesn’t send it again. Email replies to either side come over. |
Tickets that started as a chat
When a chat becomes a ticket, the customer is often still in the messenger. So with WHMCS sends its usual emails, WHMCS stays quiet about that ticket (its copies in WHMCS are written without an email), and TalkingDot emails a reply only if the customer didn’t read it in the chat, after the usual wait. Tickets that started in WHMCS or by email get WHMCS’s email for every reply.
Decided once for each reply
- Who emails a reply is decided once and stays with that reply. Changing the setting applies to new replies, so a change never sends a reply twice or drops one.
- A reply written here: decided when it is written.
- A reply written in WHMCS: TalkingDot decides as soon as WHMCS hands it over, and tells WHMCS. TalkingDot emails it only when you chose TalkingDot sends the emails, the ticket is still synced here at that moment, and the customer’s address can get emails from TalkingDot (a valid address, not unsubscribed or blocked); otherwise WHMCS emails it. WHMCS follows that answer, and asking again always gets the same answer, so exactly one of them sends it.
- While sync is paused (for example after a plan change), TalkingDot emails new replies as usual, so nobody is left without an answer.
- If a reply that WHMCS was going to email can’t get there (WHMCS refuses it for good, the ticket stops syncing, sync is paused or turned off, or WHMCS can’t be reached for 6 hours), TalkingDot emails it instead. If it reaches WHMCS later, it is added there as a note, so the customer still gets it once.
- The first import and a ticket you bring in are written quietly: they never email anyone about what was there already. A reply from WHMCS that only shows up here later, for example in the 10-minute check, is emailed from here only if it was decided that TalkingDot sends it (WHMCS then stopped its own email for it); otherwise WHMCS has emailed it already.
Don’t forward your support address to both. If support@ is piped into WHMCS and forwarded to your TalkingDot email channel, every customer email arrives twice. Pick one; the settings page warns you when this workspace receives email too.
Departments and ticket types
- Each WHMCS department becomes a ticket type here: one you already have, or a new type named after the department. We suggest a type or team with the same name.
- A department can also go to a team: tickets that come in from it are given to that team.
- Moving a ticket to another department in WHMCS changes its type here; changing the type here moves it to that type’s department in WHMCS.
- Don’t sync keeps a department in WHMCS only, for example abuse or legal. A ticket moved into it stops syncing; the copy here stays as it was.
- A department you add in WHMCS after saving these settings doesn’t sync until you switch it on. The Ticket sync card marks it New; to sync it, choose a ticket type for it in Edit settings (we pick one the same way: one with the same name, else your default department’s) and save.
Statuses
You can change these in the settings under Statuses. Your own WHMCS statuses follow their settings: active and awaiting reply means Open, active only means On hold, not active means Closed.
| In WHMCS | Here |
|---|---|
| Open, Customer-Reply, Answered, In Progress | Open |
| On Hold | On hold |
| Closed | Closed |
| Here | In WHMCS |
|---|---|
| Open (when you reopen it) | Open |
| Waiting on customer | Answered |
| On hold | On Hold (or In Progress) |
| Solved, Closed | Closed |
WHMCS marks a ticket Answered after every reply from your team, which is why Answered means Open here: the ticket stays in your inbox until you set its status. A reply to a solved or closed ticket here doesn’t reopen it in WHMCS. When both sides change the same ticket at once, the latest change wins; no message is ever lost.
Reply names and notes
- A teammate whose email matches a WHMCS admin replies as that admin in WHMCS.
- Everyone else replies as the admin you choose in the settings, and the reply ends with the teammate’s first name and your team name, like “Alex · Acme Support”.
- Replies from the AI assistant go to WHMCS too, from that admin, signed with the assistant’s name.
- A note from here starts with “{name} wrote in TalkingDot:”. A WHMCS admin’s reply or note is written here as the teammate with the same email, or with the admin’s name and “WHMCS”.
- The AI assistant doesn’t answer tickets that came from WHMCS, unless their ticket type is set to “AI first”.
Files
- Up to 10 files per message go each way.
- Files from WHMCS follow your TalkingDot file rules and storage. A file that can’t come in shows as “File not copied from WHMCS” on the message.
- Files to WHMCS are limited by your WHMCS (and at most 10 MB each). WHMCS may refuse file types it doesn’t allow for customers; the message here then says “Not in WHMCS” with the file name.
- A file pruned in WHMCS stays here if it was copied before.
What never happens
- Nothing is deleted on the other side. A ticket deleted in WHMCS is closed here with a note. A reply deleted in WHMCS is marked “Deleted in WHMCS” here and kept.
- Merging: merge synced tickets in WHMCS; the merged ticket is closed here with a note and the replies come over. Merging synced tickets here is refused.
- Turning sync off keeps every ticket as it is on both sides. Turning it on again brings in open tickets that aren’t linked yet.
- Stop syncing one ticket (in ⋯) leaves both copies as they are. Link again with WHMCS #… in its Ticket panel links it to the same WHMCS ticket again, never a new one, and quietly brings in what was written there meanwhile. Bring in a WHMCS ticket in the settings links it again too, and also brings in a closed WHMCS ticket on purpose.
- A synced conversation removed here (deleted by a teammate, or by your data retention or plan’s history limit) comes back from WHMCS only when that ticket changes there, for example when the customer replies: with its history, and the new message shown as new. A customer whose data you erase never comes back by itself.
Troubleshooting
- “Can’t reach WHMCS”: replies wait and are sent when WHMCS answers again (a reply WHMCS should email that waits 6 hours is emailed from TalkingDot instead, see above); owners and admins get a notification after 30 minutes. Click Check now in the Ticket sync card after fixing the connection (a firewall, a Cloudflare rule or a new connection code).
- “Last problem”: WHMCS answered but refused something, for example a file that is too big for it, or the import or the settings couldn’t be sent. The card shows the reason and an Error ID; sync goes on for everything else.
- “Update the WHMCS module” or “still runs the older module files”: upload module 1.3.0 and clear PHP’s cache, then Check connection.
- “Switched off in your WHMCS”: turn on Allow ticket sync in the module’s Configure page in WHMCS.
- A ticket shows “Not sent to WHMCS” or a red “WHMCS #… · failed” label: the ticket or one of its messages couldn’t go to WHMCS. The Ticket panel says why, with an Error ID, and has Retry. The error count in the settings opens all of them.
- A ticket misses a reply from WHMCS: choose Sync again with WHMCS in ⋯ to bring in what is missing. A check every 10 minutes also fills gaps by itself.
- Events pile up in WHMCS while TalkingDot can’t be reached: WHMCS keeps them and sends them from its cron, so make sure the WHMCS cron runs (every 5 minutes is usual).
- Your WHMCS moved to a new address: sync pauses and asks whether it is the same WHMCS or a new one, so tickets never end up linked to the wrong install.
Privacy and security
- Data moves only between your workspace and your own WHMCS, over HTTPS, signed with your connection code both ways and valid for five minutes.
- TalkingDot only reads and writes tickets in departments you sync. People and admins are matched by email inside your WHMCS; we never send WHMCS account numbers.
- A ticket only opens in a WHMCS client’s account by itself when the email is proven on both sides (see Tickets opened here).
- WHMCS guest tickets: anyone can open a guest ticket in WHMCS with any email address. Such a ticket joins the contact with that email here without proving the address, shows WHMCS guest ticket: email not proven, and stays out of that customer’s messenger. Check who you are talking to before you share account details.
- Unverified WHMCS accounts: anyone can also sign up in WHMCS with someone else’s address. So a ticket opened in WHMCS by a client or user whose email WHMCS hasn’t verified never joins a contact here because of its email: it gets a contact of its own, its address proves nothing here, the Ticket panel says Email not proven in WHMCS, and it stays out of the messenger.
- Text going to WHMCS is stored safely for WHMCS’s screens, so nothing a customer types can run as code in your WHMCS admin area.
- Error messages show an Error ID; ticket text and email addresses are never written to logs.