Phone
A real local number included with every agent, the advertised number diverted or ported to it, transfers to a person on the business's rules, and hours on the number's own clock.
The platform
A voice agent that picks up on the first ring, books into the diary, lodges the job, puts calls through, and sends a summary within seconds. Partners set the price.
Channels
A client's customers ring, text, type and email. The same agent answers on each, so hours, prices and services come back the same whichever way they ask.
A real local number included with every agent, the advertised number diverted or ported to it, transfers to a person on the business's rules, and hours on the number's own clock.
The same agent texts back, one question at a time, reads a photo and hands over when asked. Text campaigns and the texting API run alongside it.
The agent joins meetings in Microsoft Teams, Google Meet and Zoom from the calendar, takes the notes and sends the actions. Call notifications post into a Teams or Slack channel with plain-English routing.
One line of code puts the agent on the business's website in its own colours, typing or talking, with the conversation remembered from page to page.
Forward the enquiries inbox and every email is answered, booked, handed to a person or set aside with the reason on screen.
Telephony: how it connects to a phone system
Every agent comes with a real number, and there are four ways to put a client's calls in front of it. Routing is the platform's own to change.
Every incoming agent gets its own real local number in the region the client asks for: Auckland 09, Christchurch 03, Wellington 04, or an Australian local number. Never a number a stranger used before.
The usual setup: the client keeps its advertised number and diverts it to the agent on its own carrier. Forward all, when unanswered, when busy, or when off. The platform cannot set the divert.
A client's number can be ported in from another provider and ported back out if they leave. A ported number sits in a carrier account of the client's own, so their number leaves with them.
The platform speaks SIP end to end, so an existing SIP trunk, PBX or DDI range is connected with you during onboarding rather than through a self-serve form. How bring your own trunk works.
Porting is charged once per number, with the amount stated on the form, and a ported number answers calls to the agent; outgoing calls from it are a phone-line conversation for the briefing. Dial codes for the main carriers and the iPhone and Android menus are written up, and a divert not set is the most common support problem.
For partners with their own voice estate
The platform speaks SIP end to end: agent numbers are SIP trunk numbers, transfers go back to the carrier as SIP REFER, and team seats register as SIP softphones.
An existing SIP trunk, PBX or DDI range is connected with you during onboarding, never self-serve. Three shapes: route the DDIs or a whole trunk to the agent and leave the PBX as it is; divert selected extensions to the agent's number; or give the agent its own number and let the PBX decide when to use it.
Outbound calls and transfers go back over SIP: a transfer to an extension or a mobile is a SIP REFER to the carrier, and the onward leg is tracked so the record shows who was put through and whether they picked up. A client can bring their own number.
For distributors and SIP providers there is a tier that runs on your own carrier account and credentials, so numbers and minutes stay with the carrier relationship you hold. It is scoped with you in the briefing, not switched on from a settings page.
Bring the trunk details to the briefing: the carrier, the DDI range, how the PBX routes today and which extensions should reach the agent. We will talk through your trunk and agree the route before anything is changed.
Telephony
The clock lives on the number, calls go out as the business, and the rules on who may be rung and when sit above the client.
Campaign and automation calls show the client's own agent number, so a customer who rings back gets the same agent. Showing a number not held on the platform is not something to promise.
The client writes a per-number rule, and the record shows who was put through. After hours an on-call ladder of app alert, text, then call runs until a person accepts.
The clock lives on the number: New Zealand, the Chathams, or an Australian state. Trading hours, “tomorrow” and bookings read it, and after-hours behaviour is set on its own.
Outgoing calls are never placed before 8am or after 10pm on the clock of the person rung, and campaigns stop at 8pm. A client can narrow that window, never widen it.
Knowledge
The agent answers from what the client gives it and nothing else, under locked rules a client cannot edit out. See the knowledge base.
The client's site is crawled at deploy and re-read on a schedule afterwards. A price or opening-hours change on the site changes what the agent says without anyone editing the agent.
PDF, Word and plain text uploads, plus free-form notes, indexed in a minute or two. Scanned PDFs with no text layer cannot be read, which is worth telling clients up front.
A Local names card carries the whole New Zealand gazetteer, over four thousand place names, plus the client's own words, so the agent says them properly.
After the call
Within seconds of hanging up the client has a text and an email: who rang, what they wanted, what the agent did. See call records.
Browser push per person per device, app notifications, and call notifications into Slack, Microsoft Teams or any webhook, with plain-English routing per destination. Posts only; nothing is read back.
Recordings and full transcripts are off by default. The client switches them on per account or per agent, can switch them off again, and can delete older calls from the dashboard.
Once a week the platform proposes one change, tests it against the calls that went badly, then emails an Approve button or applies a safe wording change itself.
Hosting
The same platform runs two ways. One is built on leading AI models, the other on infrastructure the platform runs itself. You choose per client.
Leading AI models
Runs on leading AI models with enterprise-level privacy, with transcription and call analysis done locally.
Best forGetting live fast, the broadest model choice, and clients comfortable with enterprise privacy terms.
Our own infrastructure
Runs entirely on our own infrastructure, with our own hosted GPUs and our own models for voice, transcription and intelligence.
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. The choice is about where the conversation runs, not what the agent can do.
Calls are handled in New Zealand and Australian data centres, and nowhere else. That covers the call itself, the transcription and any recording. Which option suits a client is a conversation for the partner briefing, alongside their own privacy and procurement terms.
Sold through partners
Talkgate is sold through partners: managed service providers, IT companies, telcos and agencies who already look after a client's systems. You set the price and own the relationship.
Your client comes to Talkgate through you, sees the Talkgate name on the dashboard and in the summaries, and comes to you first when they need help, with Talkgate behind you. This site carries no prices, so each partner prices it as part of their own service. Partner terms are agreed in the briefing.
What the agent is for is under agents, where it talks under channels, and what comes with it under features.
Next step
A partner briefing is a working session: your clients' phone setups, the dashboard they will use, and the questions your engineers will ask.