Agents for every conversation
Talkgate puts an agent on the other side of any conversation a business has: calls in and out, texts, website chat, email, and meetings in Microsoft Teams, Google Meet and Zoom. It is sold through partners who know the client.
Escalated. On-call engineer notified, text sent.
The film
What it answers, what it does during the call, where the work goes, the API and MCP server, and the two ways to run it.
Any conversation
Eight conversations an agent can hold, across sectors and channels. The agent is the same in each; what changes is who it is talking to and where the answer goes.
Inbound callIT services
A user rings the service desk, is matched to an open ticket, and the update is written on it.
After-hours callFacilities
A building alarm at 2am is logged as urgent, and the on-call roster is worked until an engineer accepts.
Outbound callsCustomer base
Every customer on the books is rung for a short survey, each answer is read for meaning, and the ones missed get a text.
Outbound callCare provider
A daily wellness check rings each client, and their contacts are told if nobody answers.
Inbound callField services
A technician rings in from site, talks through the inspection, and the report is filed as a PDF.
Website chatAny sector
A visitor’s question on the website gets the answer the phone would give, from the same knowledge base.
EmailEnquiries inbox
A forwarded inbox is read, and each email is answered, booked or handed to a person, with the reason on screen.
MeetingSales and onboarding
The agent joins the meeting in Microsoft Teams, Google Meet or Zoom, takes the notes and sends the actions.
The idea
A conversation is still how a business gets reached when it matters, and it usually arrives while everyone is already busy with another one. Talkgate stands at that gate. A person speaks or types, the agent listens and answers, and what passes through goes wherever the client needs it: a ticket, a booking, a CRM record, a webhook into their own software, a summary, or a person on the line.
How it works
The client diverts the number on its website and letterhead to the agent, or takes a new local one. It takes a couple of minutes and nothing is installed.
First ring, any hour, in a real New Zealand or Australian voice, answering from the client's own knowledge base.
A ticket or a job in their software, a slot in the diary, a text, or a person on the line. An emergency after hours goes down the on-call ladder until someone accepts.
A summary texted and emailed to the client within seconds, every call logged in their dashboard, and the same calls visible to you as their partner.
Agents
Seven agents, one knowledge base. They are starting shapes, not the limit: each is a template a partner adapts to the conversation a client needs to hold, and a client can run more than one.
The phone agent. First ring, any hour, public holidays included. It recognises who is ringing before it says hello, answers from the client's own knowledge base, books into the diary, lodges the job, and puts a caller through when a person is needed.
More on receptionAsks the client's own qualifying questions, scores the enquiry, books a demo on the call and drops a structured lead into the CRM before the caller has hung up.
More on salesReads live availability in the client's calendar, offers real times, books on the call and reschedules while the caller is still on the line. Never a double booking.
More on bookingsOne person's own line. Answers for a director, a partner in a practice or a regional manager, works their calendar only, and passes on what matters.
More on the PAThe client writes down what counts as urgent. After hours the agent works the on-call ladder, app alert, then text, then call, until a person accepts. Voicemail never counts.
More on after-hoursRings a list the client owns, has a real conversation, flags the hot leads, honours "ring me another time" and texts the people it misses. Reminders, surveys and overdue invoices run the same way. Never bought lists, never outside calling hours.
More on outboundA field technician rings in at the end of a site visit and says what happened. The agent interviews them through the client's own form, a site inspection, an incident report, a timesheet, and the finished record is rendered to a PDF, texted, emailed and filed.
More on paperworkChannels
The same agent, with the same knowledge, answers wherever the client's customers turn up.
The main channel. A real local number, or the one the client already advertises.
Texts back on the business number, one question at a time.
Joins meetings in Microsoft Teams, Google Meet and Zoom, takes the notes and sends the actions.
One line of code puts the agent on the site, typing or talking.
Forward the enquiries inbox and every email is answered or handed on.
Features
The pieces a client notices every day, included with the platform rather than bolted on.
Calls go through to a person on the client's own rules, and an emergency after hours works down the on-call ladder, app alert, text, then call, until someone accepts. Every attempt is on the record.
Every enquiry on one board, synced to the client's CRM.
A summary texted and emailed within seconds of every call.
A weekly review of the calls that missed, and one proposed change.
Notes, documents and the client's website, read whole and re-read.
Bookings and orders on a tablet by the till while the caller is talking.
Staff ring out on the business number and the call is on the record.
Telephony
No hardware, nothing to install, and the client keeps the number on its website and letterhead.
Every agent comes with its own real local number in New Zealand or Australia, in the region the client asks for. Nobody inherits a stranger's old number.
The usual setup. The client diverts its existing number on its own carrier in a couple of minutes, or ports it in. A ported number leaves with the client if they ever go.
The platform speaks SIP end to end, so an existing trunk, PBX or DDI range is connected during onboarding. Route the numbers you choose and leave the rest alone.
Trunks and PBXsA rule per number says who gets the call and when. Trading hours and public holidays run on the clock of the number, so a Brisbane number answers on Brisbane time.
Integrations
Every connection is built and run by the platform, straight into that system. The agent recognises the caller before it says hello, and files what happened before the client has read the summary.
Xero
MYOB
HubSpot
GoHighLevel
Pipedrive
Fergus
Simpro
ServiceM8
Tradify
Cliniko
GymMaster
Google Calendar
Microsoft 365
Calendly
Freshservice
Autotask PSADevelopers
Everything the agent does is reachable from a client's own software, and from their own AI assistant.
One flexible API, with tokens scoped per ability: calls, agents, texts, replies, leads and webhooks. An OpenAPI spec partners can import into SwaggerHub, and Zapier for the rest of the stack.
The REST APILets your client's own AI assistant work the account: read calls and transcripts, edit an agent's build, draft a campaign, move leads and send a text. Every write is previewed, then confirmed.
The MCP serverHosting
One platform, two places for it to run.
Leading AI models
Best forGetting live fast, the broadest model choice, and clients comfortable with enterprise privacy terms.
Our own infrastructure
Best forClients who want the whole conversation on infrastructure the platform runs end to end, regulated sectors, and data-sensitive partners.
Both run the same agents, integrations, API and MCP server, and partners choose per client.
For partners
Talkgate is sold by the people who already look after a client's phones, IT and marketing: managed service providers, IT providers, telcos and agencies.
There are no prices on this site. Each partner prices Talkgate for its own clients, on its own terms, as one more line on the invoice they already send.
You sell it, onboard the client and give them first-line support. Your clients ring you, and you have a direct line to Talkgate when something needs escalating.
The agents, the integrations, the phone numbers and the hosting in New Zealand and Australian data centres are all run by Talkgate. You need no account with any supplier.
Data residency
Calls are handled in New Zealand and Australian data centres, and nowhere else. That covers the call itself, the transcription and any recording. Call data does not go to the United States, Europe or anywhere else.
Both countries' privacy laws recognise the other as providing comparable protection, which is what makes running across the two lawful. There is no single trans-Tasman data residency law, and Talkgate does not claim one.
Recordings and full transcripts are off by default and switched on by the client. Customer transcripts are never used to train AI models.
Next step
A partner briefing is a 30-minute call. We walk through the agents, the telephony, the integrations your clients use, where the data lives and the partner terms, and you leave knowing whether it fits your book.
