watching
recapping
refundingBuilt for · Customer support
Clear the queue.Keep your voice.
Bash triages the overnight queue, drafts the reply in your tone with the whole account in front of it, files the real bug and pings the room, inside Gmail, Slack and GitHub, as you. Nami remembers every customer — what broke before, and what you promised.
Signed in as you · 1,000+ moreOne ask. The whole queue moves.
Pick a delegation. Bash plans it, works across your tools on its own machine, and comes back with the answer, held for your word before anything reaches a customer.
WhatsAppTriage this morning’s queue↵Delegategmail · inbox · 23 overnightsalesforce · accounts · 19 matched · 4 newgmail · groups · down · blocked · question · thanksslack · post · #support-urgentEvery scene is a real delegation. The plate plays itself — pick a row to jump.
Ask from the kitchen. The queue is sorted before the kettle.
Tickets arrive before you do, so your agent starts first. Bash answers from WhatsApp, Slack, Gmail, iMessage, Telegram, or a key on your desk.
WhatsApp7:58 AM#supportMon 9:02GmailFwd
or press ctrl ctrl anywhere on your MacWorks inside your stack, as you.
Connect the shared inbox, the room and the issue tracker. A thousand more, Stripe to Zoom to Sheets, are a click away when the ticket calls for them.
Docs
Teams
Linkedin
GooglecalendarDelegate in plain words.
Paste any of these into Vestra. No setup, no syntax — it already knows your accounts, your macros and how your team writes.
Triage everything that came in overnight. Group by urgency, name the account and tier on each, and tell me who has waited longest.
Draft the reply to this thread using Fernbrook’s tier, their last three tickets and what we promised them in March. Sound like me. Hold it.
This is a real bug. Open a GitHub issue with the repro and the logs, ping #eng, and link the issue back on every ticket reporting it.
Pull last week’s ticket volume by account and type into a sheet, flag anyone trending up inside 60 days of renewal, and post it to #support.
Find every ticket older than 48 hours with no reply from us, tell me why each one stalled, and draft the apology on the worst three.
The import limit answer is wrong in three macros. Rewrite them from what shipped in issue #4412 and hold the changes for me.
On a schedule, or on a signal.
Set it once. You hear about it when it’s done — and only then.
It remembers every customer. So nobody explains themselves twice.
Tier, history, the ticket from March, the thing you promised on it. Filed once, in its place — and noticed when something changes.
Four tickets have gone 48 hours with no reply from us. Draft the apologies?
Oldest is Kestrel Freight · 3 days, 2 hoursHalcyon Labs has filed six import tickets this quarter and renews in six weeks. Brief the account team?
Enterprise · 240 seats · renews Oct 9Issue #4412 shipped this morning. Reply to the three customers waiting on it?
GitHub · merged 22 minutes agoNothing reaches a customer unread.
Every outbound reply, anything public, any credit or refund — held until you say go. Triage, research, issue filing and internal notes keep moving.
Send the reply to Deniz at Fernbrook?
You were right that we said the cap would lift this quarter. It did, on the 12th — your workspace was left on the old limit, which is on us. I am moving it this afternoon and will write back when it is done…
Install the Support playbook. Or teach it yours.
An Ability is everything the job needs — the skills, the specialist agents, the tool connections, the guardrails. Bundled, and installable in a click.
SupportQueue and replies. Triage by urgency, the account in front of every draft, your tone, nothing sent unread.TriageRepliesFollow-upTone
EscalationsThe real bugs, filed properly. Repro, logs, the accounts affected, and the issue linked back on every ticket waiting.ReproIssuesStatus
Create your ownYour playbook, encoded. Teach it what you escalate, how you apologize, when you refund — in plain words.Your rulesYour voiceCustomer support · FAQ
Questions, answered.
Does it reply to customers on its own?
Will it sound like our team, or like a bot?
How does it know a ticket is a real bug?
What does it know about our customers on day one?
Where does the work run?
Built for the way the rest of the office works, too.
The door
Come back to answered.
Send us a week of your queue. We’ll show you what Bash would answer, what Nami would keep, and what’s actually left for you.