Runbook
Tasks tonight1,284
02:16Ticket #772 closed
02:16Ticket #772 closed
02:16Ticket #772 closed
Part 01 / 04What it does
What runswhile nobody is in.
Every message to support is read, tagged by topic and urgency, and answered from your own help articles when the answer already exists. Refunds, cancellations and outages go to a person within minutes with the customer's history attached. Across our clients 71 % of tickets close without anyone on their side touching them.
What you get
- 01The workflow built in your own accounts, documented and yours to keep
- 02A test run on real records before anything goes live
- 03A log line for every run and an alert to us when one fails
- 04A person watching the first week, then the monthly care plan
Part 02 / 04How it runs
Trigger, steps,result.
Every run follows the same drawn path. A step that cannot complete parks the record for a person and says why.
- TriggerA record changes in your tools: a job closes, a form lands, a message arrives.
- 01ReadThe record is read from the tool it lives in: who, what, how much.
- 02CheckRules run against it. Anything odd is parked for a person, nothing odd is parked for nobody.
- 03ActThe document is built, the message sent, the field updated, in your own tone.
- 04LogOne line in the night log, with the time and the outcome, so you can read what ran.
- Result02:16 · Ticket #772 closed
Part 03 / 04Tools
The toolsit runs on.
Runs on
- Intercom
- Zendesk
- Help Scout
- Slack
- Notion
CommsUsed in 5 workflowsInbox
Mail read, sorted and drafted before you open it.Connects toGmail, Outlook, Slack
DataUsed in 3 workflowsDocs
Contracts, folders and boards created the moment they are needed.Connects toNotion, Google Drive, DocuSign- SupportUsed in 2 workflows
Helpdesk
Tickets tagged, answered from your own articles and escalated with the history attached.Connects toIntercom, Zendesk, Help Scout
Part 04 / 04Results
What it didfor others.
Part 01 / 04What it does
What runswhile nobody is in.
Every message to support is read, tagged by topic and urgency, and answered from your own help articles when the answer already exists. Refunds, cancellations and outages go to a person within minutes with the customer's history attached. Across our clients 71 % of tickets close without anyone on their side touching them.
What you get
- 01The workflow built in your own accounts, documented and yours to keep
- 02A test run on real records before anything goes live
- 03A log line for every run and an alert to us when one fails
- 04A person watching the first week, then the monthly care plan
Part 02 / 04How it runs
Trigger, steps,result.
Every run follows the same drawn path. A step that cannot complete parks the record for a person and says why.
- TriggerA record changes in your tools: a job closes, a form lands, a message arrives.
- 01ReadThe record is read from the tool it lives in: who, what, how much.
- 02CheckRules run against it. Anything odd is parked for a person, nothing odd is parked for nobody.
- 03ActThe document is built, the message sent, the field updated, in your own tone.
- 04LogOne line in the night log, with the time and the outcome, so you can read what ran.
- Result02:16 · Ticket #772 closed
Part 03 / 04Tools
The toolsit runs on.
Runs on
- Intercom
- Zendesk
- Help Scout
- Slack
- Notion
- CommsUsed in 5 workflows
Inbox
Mail read, sorted and drafted before you open it.Connects toGmail, Outlook, Slack - DataUsed in 3 workflows
Docs
Contracts, folders and boards created the moment they are needed.Connects toNotion, Google Drive, DocuSign - SupportUsed in 2 workflows
Helpdesk
Tickets tagged, answered from your own articles and escalated with the history attached.Connects toIntercom, Zendesk, Help Scout
Part 04 / 04Results
What it didfor others.
Part 01 / 04What it does
What runswhile nobody is in.
Every message to support is read, tagged by topic and urgency, and answered from your own help articles when the answer already exists. Refunds, cancellations and outages go to a person within minutes with the customer's history attached. Across our clients 71 % of tickets close without anyone on their side touching them.
What you get
- 01The workflow built in your own accounts, documented and yours to keep
- 02A test run on real records before anything goes live
- 03A log line for every run and an alert to us when one fails
- 04A person watching the first week, then the monthly care plan
Part 02 / 04How it runs
Trigger, steps,result.
Every run follows the same drawn path. A step that cannot complete parks the record for a person and says why.
- TriggerA record changes in your tools: a job closes, a form lands, a message arrives.
- 01ReadThe record is read from the tool it lives in: who, what, how much.
- 02CheckRules run against it. Anything odd is parked for a person, nothing odd is parked for nobody.
- 03ActThe document is built, the message sent, the field updated, in your own tone.
- 04LogOne line in the night log, with the time and the outcome, so you can read what ran.
- Result02:16 · Ticket #772 closed
Part 03 / 04Tools
The toolsit runs on.
Runs on
- Intercom
- Zendesk
- Help Scout
- Slack
- Notion
- CommsUsed in 5 workflows
Inbox
Mail read, sorted and drafted before you open it.Connects toGmail, Outlook, Slack - DataUsed in 3 workflows
Docs
Contracts, folders and boards created the moment they are needed.Connects toNotion, Google Drive, DocuSign - SupportUsed in 2 workflows
Helpdesk
Tickets tagged, answered from your own articles and escalated with the history attached.Connects toIntercom, Zendesk, Help Scout
Part 04 / 04Results
What it didfor others.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.