Does Dixa answer the phone?

Yes — a human in Team Hub (Dixa’s agent workspace) can. Native voice sits next to email and chat in the Dixa workspace. That is on Dixa’s voice page today (read 19 September 2026): browser calling (VoIP — voice over the internet, no desk phone), an interactive voice response (IVR) phone menu in the same Flow Builder as other workflows, callbacks that keep queue place, voicemail in the same queue, and automatic transcripts.

Does Mim pick up? Treat that as a different sentence. Dixa’s Q2 2026 roadmap (still the latest public recap as of 19 September 2026) called Mim on Voice foundations / Beta, with first customers planned for Q3 and major EU languages first. The early build covered interruptions, order-number confirm, and silence. Dixa’s next roadmap session is listed for 29 September 2026 — ask Dixa whether Mim answers your queue before a deck says “AI voice.”

Someone calls the store. You already bought Dixa. The question is not “does Dixa have a phone channel.” It is “who answers — a person in Team Hub, Mim if your workspace is in the Voice rollout, or nobody after hours.”

What Dixa’s site actually says about the phone

Dixa is a unified conversation desk. Voice, email, chat, and social share one workspace, one customer card, one routing and reporting model. Shopify shows up in the Q2 2026 roadmap as an ecommerce integration they keep improving (with Yotpo and Klaviyo). Humans get a real phone channel in Team Hub. That is native telephony — not a partner dialer glued on later.

Mim (Dixa’s AI agent) is documented on dixa.com/ai-agent for chat, email, WhatsApp, Messenger, and SMS: refunds, tracking, order changes, FAQs, then handoff. That public Mim page does not put Mim on every inbound line. Jakob Nederby Nielsen, Dixa’s CEO, wrote on 22 June 2026 that they had intentionally held off putting AI on voice, and framed the fit as after-hours, queue overflow, callback orchestration, and surge capacity — not “AI replaces the phone team.” That June note is the hold-off. The Q2 roadmap is the later foundations / Beta work — sequence, not a contradiction, and not general availability.

Verdict: the channel is real; Mim-on-the-line is a workspace-specific status, not a homepage checkbox.

Mim on Voice is a rollout, not a checkbox

Dixa spent Q2 laying technical foundations. Q3 was the “first customers” story. Mid-September 2026 is still inside that Q3 window, and we did not find a public GA announcement that every Dixa customer’s store number is covered. Beta language, EU-language-first, and “switch on by queue” are the opposite of that.

If Mim already answers your overflow queue in the languages you need, stay there. You do not need a second AI for that slice. If the store number still rings a person — or rings nobody after close — that is the gap this post is about. A published-plan storefront agent in front of Dixa is only the third row in the table below — not a reason to rip Team Hub.

The storefront job Dixa is not trying to be

Dixa sells the workspace. A front-line agent does not replace Team Hub. It trains on help articles and solved tickets from Salesforce, Zendesk, or the desk you already run, publishes the website widget, and forwards the store number — always, or only after hours / no-answer / busy. Handoff can open a ticket in Salesforce, Zendesk, or Guzli’s help desk.

A tracking question Mim already handled in Dixa chat should not become a different answer on the store number after close. That match is the job when Mim-on-Voice is not ready for your queue and you still need the widget and the line to agree.

Desk shopping: Dixa alternatives. Nearby “does it answer” read: Does Intercom Fin answer the phone?.

Keep the workspace. Cover the line.

Do not rip Dixa to “get phone AI.” Keep the desk. Put Guzli on the storefront and the forwarded number when Mim-on-Voice is not ready for your queue.