Toku

Toku is a Singapore-headquartered cloud communications company that provides bespoke communication and engagement solutions for enterprises.

Team size
201-1000
Request a quoteContactVisit website

Overview of Toku

Specialization
Cloud Communications (CPaaS/UCaaS/CCaaS)

Toku is a Singapore-headquartered cloud communications company that provides bespoke communication and engagement solutions for enterprises. The company offers AI-powered solutions, business telephony, customer engagement tools, and embedded communications for voice and messaging. Toku's offerings include AI for productivity, conversational AI, AI voice agents, and integrations with platforms like Microsoft Teams and Zoom Phone. It also provides contact center solutions, campaign management, and feedback management systems. Toku supports enterprises in the Asia-Pacific region with locally compliant communications and aims to enhance customer and employee engagement through AI-powered solutions.

  • Recorded Singapore presence: Physical Singapore office
  • Website: https://toku.co/
  • Capabilities: AWS
  • Tech ecosystem: AWS (Advanced)

Profile updated 10 Jul 2026 Report incorrect data

Buyer Decision Checklist

Before you compare price-per-user, decide which job you're buying for — hosted PBX, SIP trunking into Teams, or a cloud contact centre — then pressure-test each Singapore provider on numbering, emergency calling, and call-quality support.

How to evaluate a VoIP / cloud telephony provider in Singapore

  • Decide which of the four jobs you have before talking to anyone: hosted/cloud PBX for general office lines, SIP trunking into your own PBX or Teams Direct Routing, CCaaS for sales/support queues, or CPaaS voice APIs — buying the wrong category is the most expensive VoIP mistake.
  • Confirm the provider can issue new +65 DID numbers and port your existing ones under IMDA number-portability rules, and get the porting timeline in writing (typically 5-10 business days) plus a cutover plan that keeps the old service live until the port completes.
  • Pin down emergency-calling (995/999) behaviour and ask whether they hold the relevant IMDA FBO or SBO licence for number allocation, interconnection, and emergency-call obligations — a pure overseas SaaS may not route emergency calls correctly from a Singapore address.
  • If you record calls, map the deployment to PDPA: get a clear answer on where call recordings and CDRs are stored, who can access them, retention periods, and whether in-region storage and cross-border transfer terms are available if your policy requires it.
  • For Microsoft 365 shops, verify they explicitly certify Teams Direct Routing with a supported SBC, and confirm they can supply or port +65 numbers into Teams rather than forcing a second phone app.
  • Define call-quality monitoring and post-go-live escalation up front: ask about QoS/codec/jitter handling, what dashboards or MOS reporting you get, and who owns a sev-1 voice-down ticket with a named Singapore-based contact and response SLA.

Verify for Toku

  • Confirm key details directly with the vendor — this listing isn't vendor-managed yet.
  • Ask for two recent Singapore client references you can speak with.
  • Ask for a written scope of services before comparing quotes.
  • Request evidence of relevant certifications and their current validity.

Questions to ask

  • Can you issue new +65 DIDs and port our existing numbers, and what is the realistic porting timeline and cutover plan?
  • How are 995/999 emergency calls routed from a Singapore location, and which IMDA licence (FBO or SBO) do you hold?
  • Where are call recordings and CDRs stored, who can access them, and can storage stay in-region for PDPA?
  • Do you certify Teams Direct Routing with a specific SBC, and who is the named local contact for a voice-down escalation?

Prepared under the TechDirectory editorial byline with review credit June C; this label is not proof of identity, credentials, or a completed human review. This directory-authored checklist is not attributed to Toku; editorial independence has not been independently audited. Editorial standards

5/100

Profile signal score

Based on recorded profile signals. It is not a certification or independent verification of every claim, and it does not measure vendor quality or endorsement; paid plans do not affect it. How it works.

  • UEN recorded on profile No UEN recorded 0/20
  • Owner-claimed profile No owner claim recorded 0/10
  • Recorded grant eligibility None recorded 0/15
  • Recorded CSA trustmark None / expired 0/15
  • Listed certifications None listed 0/10
  • Approved reviews No approved reviews yet 0/20
  • Profile completeness 5/10 completeness 5/10

Similar vendors to compare