Dixa logo

Dixa + Memtro

Ask what a customer contacted support about, with the messages, notes and ratings from Dixa.

Connect Dixa with an API token and Memtro reads conversations by words, status, queue, agent and date, with messages, internal notes and CSAT or NPS ratings, end users found by email, phone or external id, and agents, queues and tags. Attachments are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can reply to a customer or email one as a named agent, which cannot be unsent, add internal notes, close, transfer, assign and tag conversations, and permanently anonymise an end user.

In Memtro

What you can do with Dixa in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Dixa tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Conversations by words, status, queue, assigned agent, created date or last activity, up to 25 at a time
  2. 02One conversation with its messages, internal notes and CSAT and NPS ratings, without attachments
  3. 03End users found by exact email, phone number or external id, with their conversations
  4. 04Agents with their roles, queues with the default marked, and conversation tags
  5. 05When asked and granted, replies to a customer on the conversation's channel or emails a customer to start a conversation, written as the agent you name, which cannot be unsent, and adds internal notes agents see but customers do not
  6. 06When asked and granted, closes, reopens, transfers, assigns, tags and sets follow-ups and attributes on conversations, offers a satisfaction rating, creates or updates end users, and permanently anonymises an end user on request

Acts when asked

When you ask it to

These tools change something in Dixa. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.

  1. 01Add an internal note to a conversation, never sent to the customer
  2. 02Reply to the customer in a conversation as a named agent
  3. 03Start an email conversation with a customer (the first message is emailed)
  4. 04Close a conversation
  5. 05Reopen a conversation in its queue
  6. 06Transfer a conversation to another queue
  7. 07Assign (claim) a conversation for an agent
  8. 08Add or remove a tag on a conversation
  9. 09Set a follow-up time on a conversation
  10. 10Set custom attribute values on a conversation
  11. 11Offer a satisfaction rating to the customer
  12. 12Create a conversation tag
  13. 13Create an end user (customer record)
  14. 14Update an end user's name, email or external id
  15. 15Anonymise an end user (permanent erasure)

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Dixa for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Dixa signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01A conversation was created
  • 02A closed conversation was reopened
  • 03A conversation was set pending with a follow-up
  • 04A conversation's follow-up expired
  • 05A conversation was closed
  • 06A conversation closed with no agent assigned
  • 07A conversation entered a queue
  • 08A conversation was assigned to an agent
  • 09A conversation was unassigned
  • 10A message was added to a conversation
  • 11An internal note was added
  • 12A tag was added to a conversation
  • 13A tag was removed from a conversation
  • 14A customer rated a conversation
  • 15A conversation was transferred
  • 16A conversation's custom attribute changed
  • 17A call transcription was added
  • 18An SLA was breached
  • 19An SLA was met
  • 20An SLA started counting
In practice

Ask it like you would a colleague

Once Dixa is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.

Dixa logoDixa + Memtro
  • What did Acme contact support about last week?

  • Which conversations in the billing queue are still open?

  • How did the customer rate the conversation Priya Nair handled yesterday?

  • Reply to conversation 4812 as Priya that the refund went out today

  • Transfer the Globex conversation to the billing queue

01

Before the renewal call

Before a renewal call the account lead asks what Brightwave Ltd has raised with support this quarter. Memtro finds the end user by email and lists four conversations, two about invoices and two about login problems, each with its queue, agent and rating.

02

Answering the customer

Support lead Priya Nair asks Memtro to tell the Acme customer in conversation 4812 that finance approved the refund. Memtro shows her the reply, and once she approves the words it sends it as Priya on the conversation's own channel, where the customer receives it straight away.

Teams

Where it fits

The teams that lean on Dixa most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Dixa is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.

Setup

How to connect

Connect withAPI token
  1. 1

    In Dixa open Settings → Manage → Integrations → API Tokens and add a token with the API version Dixa API. Only a Dixa administrator can create one

  2. 2

    Tick the permissions Memtro should have: conversation.reply to add notes, reply, start, close, reopen, transfer or follow up conversations, conversation.claim, conversation.tag, settings.tag, organization.member and the others only for the actions you will grant, and anonymization only if Memtro may anonymise an end user

  3. 3

    In Memtro open Connections → Dixa, paste the API token and connect

  4. 4

    Ask what Acme contacted support about last week

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Dixa tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in Dixa?+

Only when you ask, and only what it has been granted: add an internal note to a conversation, never sent to the customer; reply to the customer in a conversation as a named agent; start an email conversation with a customer (the first message is emailed); close a conversation; reopen a conversation in its queue; transfer a conversation to another queue; assign (claim) a conversation for an agent; add or remove a tag on a conversation; set a follow-up time on a conversation; set custom attribute values on a conversation; offer a satisfaction rating to the customer; create a conversation tag; create an end user (customer record); update an end user's name, email or external id; anonymise an end user (permanent erasure). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

Who can use a Dixa connection?+

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Does Memtro store my Dixa data?+

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

How do I connect Dixa?+

API token. In Dixa open Settings → Manage → Integrations → API Tokens and add a token with the API version Dixa API. Only a Dixa administrator can create one.

Can Dixa start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Dixa for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.

Connect Dixa in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time