Skip to main content
On a phone, CRM → Conversations works like a messaging app: one thing at a time — the inbox, a thread, a contact’s details — with every menu, filter and confirmation as a sheet you can swipe away. Nothing from the desktop page is missing; it is re-arranged for a thumb and an on-screen keyboard. Open dashboard.dialtu.com in the phone’s browser and sign in as usual. On a phone you land on the inbox straight away. To keep it one tap away, add the page to your home screen from the browser’s share menu.
The phone layout switches on below 768 px wide. Between 768 and 1023 px (tablets) the inbox stays beside the thread; from 1024 px you get the three-pane desktop page.

The three screens

1

Inbox

The list of conversations. Tap a row to open it.
2

Thread

The messages, the composer and — in the header — who is handling the conversation. Tap the name, the session strip or the button to open the contact’s details.
3

Contact details

Everything the desktop right-hand panel shows: contact, human support, Salesflow, tags, active automations, Activity and Notes.
in the header, or the phone’s own back gesture, always goes back one screen. Each screen has its own address, so a link or a notification can open a thread directly — Back from there still takes you to the inbox.

The inbox

Phone inbox: header with the menu button, Conversations title, Live indicator, mark-all-read button with a badge and add-client button; a search field and filter button; All, My Inbox and Unread tabs; a list of conversations with avatars, channel badges, names, previews, times and unread counts

The inbox — ≡ opens the app menu; the check badge counts conversations with unread messages

The header carries the app menu (), the Live / Offline indicator, Mark all as read (its badge counts the conversations with unread messages) and Add client. Below it, search, the filter button and the All · My Inbox · Unread tabs. Each row shows the avatar with the channel badge (green WhatsApp, blue SMS, purple voice), the name in bold when unread, a Transfer / Review / New chip when it applies, the time, then the handling icon (robot = the AI is replying, person = a teammate is), the last message, the assignee’s initials and the unread count. The phone number moved to the thread header.

Gestures

The Lucía Ferrer row swiped to the left revealing a purple Read button and a grey Unread button

Swipe left on a row for Read / Unread; a full swipe marks it read

A bottom sheet titled Nora Bennett with her phone number and the options Open conversation, Mark as read and Open client detail

Long-press a row for its menu

The filter sheet has the same four controls as the desktop menu — Tags, Assignee and Pipeline stage drill into their own lists, Needs attention is a switch. Filters apply as you change them; Apply closes the sheet and Cancel restores what you had.
A bottom sheet titled Filter by with rows for Tags, Assignee and Pipeline stage, a Needs attention switch, and Cancel and Apply buttons

The filter sheet

Live updates

The list updates in real time. If the connection drops, Live turns into Offline and a Connection lost — reconnecting… strip appears under the header until it recovers. When new activity arrives while you are scrolled down, a conversations with new activity pill floats over the list — tap it to jump to the top with a fresh list.

The thread

Phone thread screen: back arrow, avatar, Lucía Ferrer and her number, an actions button and an info button; a strip reading SMS Session, Human handling, Lumina, Order support; customer and agent bubbles, a tool card and a system note; an amber banner reading You're handling this conversation with a Return to AI button; an input row with the SMS chip, a plus button, the Message field and a send button

An SMS thread a teammate is handling — the header, the session strip, the messages and the composer

The session strip is the desktop session header on one line — channel, who is handling, engine, agent, and for calls the direction, status, duration and disposition. Swipe it sideways if it is longer than the screen. Messages look exactly as on the desktop: customer on the left, the AI and your team on the right, tool executions as cards, system notes as centred pills. Scroll up to load older messages; a jump to latest button with an unread count appears while you are scrolled up. On WhatsApp, tap the small reply arrow beside a message to quote it in your reply.
A bottom sheet titled Actions with a search field and the rows End Session in red, Return to AI, Mark as unread, Edit customer name, Copy phone number and Open client detail

The ⋯ actions sheet

The actions sheet gathers what lives in several places on the desktop: End Session, Take Over or Return to AI (whichever applies), Mark as unread, Edit customer name, Copy phone number and Open client detail. It is searchable.

The composer

The composer is one banner row and one input row. The banner says who is handling the conversation and carries the one button that changes it; the input row holds the channel chip, +, the message field and mic or send.
A WhatsApp thread with an amber banner reading You're handling this — the AI has stopped replying and a Return to AI button, above an input row with the green WhatsApp chip, a plus button, an empty Message field and a microphone button

Human handling on WhatsApp — the mic shows while the field is empty

A bottom sheet titled Reply on listing WhatsApp with the sending account, SMS and Voice, then a Sending from section with three phone numbers, the selected one checked

Reply on — the channel and the sending number

A bottom sheet titled More with rows Photo or video, Document, Predefined messages, Scheduled messages and Schedule message

More — attachments, predefined and scheduled messages

The composer with a three-line message typed in the field, a purple send button on the right

Typing — the field grows and Send replaces the mic

Who is handling

  • AI handling — a purple banner with Take Over. The field is closed until you take over.
  • Human handling — an amber banner with Return to AI (or Have AI take control when the session never had an agent).
  • No session — a Start WhatsApp chat button, or the opening-message field and Start SMS Chat on SMS.
The 24-hour WhatsApp window works as on the desktop: when it has closed, an amber row replaces the field and Send a template is the only way to write.
A WhatsApp thread with a purple banner reading Session active (AI handling) and a Take Over button, then an amber row reading 24-hour window closed — templates only with a Send a template button; the input row shows only the channel chip and the plus button

AI handling with the 24-hour window closed

Ending a session

⋯ → End Session asks how the customer is told the conversation is over — a generic closing message, one written by the AI, one you type, or ending without a message. SMS sessions end without a closing message.
A bottom sheet titled End session? with radio options Generic closing message, Let the AI write a closing message, Type my own message and End session only, plus Cancel and a red End Session button

End session — the closing-message choice

Calls

Pick Voice in the channel sheet, or open a past call from Activity: the transcript shows the AI summary and the recording at the top, and the composer becomes the agent picker, call settings and Start Call.
The thread screen for a call: strip reading Inbound Call, Completed, duration and Agent Sarah; an AI call summary card; the transcript with agent, customer and tool bubbles; at the bottom an agent picker, a settings button and a Start Call button

A completed call opened from Activity, with the voice composer below

Contact details

Contact details screen: back arrow, Lucía Ferrer, Regenerate memory and Open client record buttons; cards for phone with a Call link and email, Keep on human support with a switch, Salesflow with Add to pipeline, Tags, Active automations with an SMS session, and Activity and Notes tabs with a filter button

The contact's details as a screen of its own

Tap the phone number to call it from the phone. The header’s two buttons regenerate the AI memory and open the full client record. Keep on human support is a switch. Salesflow, Tags and Active automations behave as on the desktop — tap a session under Active automations to open it. Under Activity, tap any past call or chat to open its transcript in the thread; the details screen closes by itself. The filter button opens period, type, agent and disposition tag as a sheet.
A bottom sheet titled Filter activity with period chips 7 days, 30 days, 90 days and All time, type chips All, Calls, WhatsApp and SMS, an agent list with All agents checked, and Cancel and Apply buttons

The Activity filter sheet

Sheets

Every menu, filter and confirmation opens as a sheet from the bottom of the screen. Close one by dragging its handle down, tapping outside it, or pressing the phone’s Back — Back closes the sheet first and never leaves the thread, so a message you were typing is still there.

Tablets

Between 768 and 1023 px the inbox stays on the left and the thread fills the rest; there is no back arrow. The contact’s details slide over from the right — tap outside to close them, or tap an Activity item to open that session behind them.
Tablet layout with the inbox list in a 320-pixel column on the left and the SMS thread with its composer on the right

A tablet: the inbox beside the thread

The same tablet layout dimmed, with the contact details panel sliding in from the right edge

Contact details slide over the thread on a tablet

The Conversations inbox

Statuses, taking over and handing back, on the desktop page.

Assignment

How conversations end up in My Inbox.