Skip to content

After the call

Every call, written up in seconds.

The owner finds out what happened on the phone when somebody remembers to mention it. The message pad has a first name and half a number. The recording, if there is one, is on a handset nobody checks.

Book a partner briefing All features
the calltranscriptcalleragentcalleragentcalleragentcallersummarywho rangwhat forwhat was donesent within secondsrecorded if switched on
A transcript and a summary of who rang, what for and what was done, sent within seconds.

What the platform does

Summarises, notifies, records on request, and keeps getting better.

The call is over. Within seconds the business knows who rang, what they wanted and what was done about it.

A summary within seconds

A text and an email after every call: who rang, what they wanted, what the agent did. In the inbox before the caller has put the phone down.

Notifications where the team already looks

Browser push per person per device, app notifications, and posts into Slack, Microsoft Teams through a Power Automate flow, or any webhook. Routing is written in plain English per destination. The platform posts and reads nothing back.

Recordings and transcripts, on the client's terms

Off by default. The client switches them on per account or per agent, switches them off again, and deletes older calls from the dashboard. Call metadata is kept either way.

Every call marked

Against the business's own definition of a good call: three plain-English questions by default. The dashboard shows which calls passed and which did not.

Confirmations to the customer

Email confirmations to the caller, written fresh each time from a brief the owner sets, and marked as a booking or an enquiry so the customer knows which they have.

Reviewed every week

The calls that missed are read back once a week and one change is proposed, tested against those calls first. The whole of that is on its own page: call quality.

How it goes after the call

From hang-up to a better agent next week.

  1. The call ends. Within seconds the summary is texted and emailed, and a push notification reaches whoever is set to receive one.
  2. It is posted where the team works. Slack, Teams or a webhook, according to the plain-English routing for each destination.
  3. It is written into the connected system. A note on the CRM contact, a private note on the ticket, a communication note on the patient file, a note on the overdue invoice.
  4. It is logged in the dashboard. Metadata always: who rang, when, how long, what happened. Recording and transcript too, if the client has switched them on. Marked against the good-call definition.
  5. The week is reviewed. The platform looks at the calls that missed, proposes a change, tests it against those calls, and either asks for approval or applies a safe wording fix. See call quality.

What the business gets

A record of every conversation, in the places it is needed.

The summary goes to people. The detail goes to systems. Nothing depends on anyone remembering.

  • Transcript, summary and answers logged on the contact in HubSpot, GoHighLevel or Pipedrive, and a card per lead in Trello.
  • A call summary noted on every ticket touched in Freshservice or Autotask PSA, both in early access.
  • The call written up as a communication note in Cliniko, with no clinical detail ever read.
  • A note on the invoice in Xero after an overdue-account call.
  • Every enquiry filed in the leads list with the call and text history for that number beside it.
  • A “How it works” map showing where every piece of information goes and how long it is kept.

What you see in the dashboard

  • Every call for every client organisation, with its summary, its marking, and its recording and transcript where switched on.
  • Browser push and app notifications per person per device, so the right people hear about the right calls.
  • Roles that fit how a partner works: a company owner per client, and company staff narrowed to the agents they are allowed to see.
  • Your named person gets into a client's account only if the business ticks the box, and the business can remove them under Team without asking anyone.
  • Calls, transcription and recordings handled in New Zealand and Australian data centres, and nowhere else. Transcripts are never used to train anything. See security.
An IT service desk at night with two switched-off monitors, a desk phone and a lamp, rain on the window
A service desk after hours. The summary is in the inbox before anyone is back at the desk.

Sold through partners

The part of the service clients show their own staff

Summaries, notifications and the dashboard are not an extra. They are what makes the phone agent feel like a member of staff rather than a machine. The weekly call quality review is the quiet reason an agent sold in March is better in June without a change request. Sold through partners: you set the price, Talkgate runs the platform. Package the recordings and the weekly review as part of a managed service, or hold them back for the clients who ask. See the partner programme.

Works with

Posts to the team, writes to the systems.

Every connection is built and run by the platform, straight to that system. See all integrations.

Next step

See a call land in the dashboard as it ends.

A partner briefing shows the summary arriving, the routing into Slack or Teams, the dashboard, and a call quality proposal.

Book a partner briefing Or see the knowledge base