Use case · Support
Answer tickets with the whole company behind you
Support teams spend their day switching tabs: the ticket in Help Scout, the customer in the CRM, the order in the warehouse, the invoice in Xero. Memtro reads the ticket and does the switching for them.
The problem
- Context lives in five systems and the agent has access to two
- The same customer history is rediscovered every time they write in
- Escalations lose detail on the way to engineering or finance
How Memtro helps
- Ask about a ticket and agent mode pulls out the customer, order numbers and dates, then checks the CRM, databases, billing and email before answering
- Every answer ends with a line per system consulted, so nothing is assumed
- Customers, tickets and orders are anchored into memory, so the second question is faster than the first
Example queries
- › Have a look at Help Scout ticket #2450
- › Which VIP conversations have been waiting more than a day?
- › What has Sam Lee contacted us about this year, and are any invoices overdue?
Jobs to schedule
- schedule: Every weekday at 9, summarise VIP tickets older than a day with the customer's account status
- schedule: Every hour, flag new conversations from customers with an open invoice dispute
Say any of these in Chat and Memtro creates the job. See Jobs.