Summary
Customer context, before the call.
The five minutes before a customer conversation — who they are, how healthy the account is, what was said last, what is still open — become a couple of calls, and whatever you learn goes back as a note.
What it is
A reader for Vitally customer data, with one write. Accounts are searched by name or external ID and users by email; an account's health score, conversations and tasks come back separately, and notes can be created against an account.
What you get
- Accounts searched by several criteria, or found by partial name
- Users searched by email or external ID
- An account's health score read
- The conversations on an account, and the tasks still open against it
- A note created against an account
- The cached account list refreshed, and the available tools searched by keyword
Requirements
Node to build it, and your Vitally subdomain, API key and data centre — US or EU — set in the environment. Without a key it starts in demo mode against mock data, which is enough to see the shape of the answers.