The same phone number across two threads and a missed call comes back as one situation. The draft answers the whole question instead of the last two-word fragment.
WhatsApp support arrives in fragments, half a sentence at a time, often over three days, and the same customer opens a new thread rather than scrolling up. By the time you answer, the actual question is spread across four messages and two threads.
A companion reads tickets, contacts, teams and labels across every channel you run and puts the question back together. Everything it changes is staged for you first.
01
What does a companion do with fragmented threads?
Reassembles them into a question.
It pulls the open tickets with their contacts and channels, notices the same phone number across two threads and a missed call, and reports one situation instead of three tickets. The draft then answers the whole thing.
Anyone who has answered a two-word WhatsApp message with a paragraph and received "no, the other one" knows why this matters. Rules have nothing to match on. The information is in the words.
02
Can it keep the labels usable?
Ask for the label list with volumes and a companion returns the near-duplicates, the ones used once in March, and the tickets with no label at all. Relabelling is staged as one proposal you read.
The reason to bother is reporting. Nobody can answer "how much of our volume is delivery questions" if delivery, deliveries and Delivery all exist, and nobody notices until it is asked in a board meeting.
03
Reading load instead of counting open tickets
A companion reads who is assigned what and how long each ticket has waited, which is an honest picture of load. Two people with fifteen tickets each are not equally busy if one holds every escalation.
It reports, you rebalance. Assignment changes wait for confirmation, which for a rota conversation is the right speed. The support-week version is ai for support teams.
04
WhatsApp is not email, and the template rules bite
The twenty-four hour reply window and the approved-template requirement are platform rules, enforced by Trengo and the WhatsApp Business platform.
A companion watches the clock for you and says when a conversation is about to fall outside the window, while there is still time to send something a person wrote.
Yes, through a connected Trengo account. A companion reads the tickets and contacts across channels, which is how it notices that two threads and a missed call are one customer.
Yes. Connect the account and a companion reads tickets, contacts, teams and labels across every channel you run, so one phone number in three threads comes back as one situation. Its actions come from Trengo’s public API.
Ask for the label list with volumes and the near-duplicates named. Relabelling arrives as one proposal covering every affected ticket, and it waits for your confirmation.
It reports load honestly, including how long each ticket has waited and who is holding the escalations. Reassignment needs your approval, which is the right speed for a rota conversation.
It drafts the reply covering the whole fragmented thread rather than the last message. Sending goes through Strawberry’s confirmation controls every time.
Trengo Strawberry