Skip to content
[ hire mara ]

Chat

Chat is how you direct Mara. It is a conversation in your dashboard where you ask her to design programs, write and edit emails, build segments, approve or reject her drafts, and teach her what works. She streams a reply, and when she takes an action she shows it inline so you can see what changed.

What you can do

  • Ask Mara to design a program for any moment in your customer lifecycle, or to set up a whole program. She drafts it and you approve before anything goes live.
  • Edit an existing program: change the copy, the timing, the segment, or the trigger. Every edit comes back to you to re-approve.
  • Build a segment from your contacts and their behavior, then attach a program to it.
  • Approve or reject what Mara has drafted, including programs and the variant sets she proposes for testing.
  • Pause, resume, or archive a program from the conversation.
  • Manage your Playbook, the set of learnings that shape how Mara writes. Ask her what she has learned, add a learning, or retire one.
  • Fix a send problem without leaving chat: rewrite or retire an email variant, add a suppression, or clear failed sends.
  • Ask what is happening: which programs are active, what has been sent, and why a send failed.

How

Open chat from anywhere in your dashboard (it docks beside the page, floats over it, or tucks into a small bubble, whichever you prefer) and type what you want, in plain language. You do not need to name a tool or learn any syntax. Mara figures out what to do.

  • When she takes an action, it appears inline in the conversation as a collapsible step, so you can expand it to see exactly what she did.
  • Actions that change what gets sent are gated. Mara drafts, and the draft waits for your approval before it sends. You stay in control.
  • Some cards elsewhere in the dashboard hand you off to chat with the context already filled in, for example an idea from Mara or a failed send you want to ask about. Approving from there runs the same conversation.
  • Long conversations stay coherent: Mara works from a running summary of the earlier messages plus your most recent ones. Start a new chat anytime for a clean slate, and use the history dropdown to jump back into a past conversation.

Limitations

  • Chat does not send data into Mara. Connecting your product (who your users are and what they do) happens through the Mara API and webhooks, covered in the developer docs.
  • Mara will not skip your approval on anything that sends. She drafts; you decide. Approving is always a deliberate step.
  • She acts only on your own workspace. She cannot see or touch another company's contacts, programs, or data.
  • Mara reaches for a tool before she tells you she cannot do something. If she says a request is out of scope, it is because no tool covers it yet, not because she did not look.
  • Chat is for directing the program. To read what a program sends step by step, the Programs pages lay it out without a conversation.