Muriki
All use cases
use case

Sales and support

From first contact to resolved ticket, with the history intact.

In sales and support the context is always in another tab: the conversation in email, the agreement in chat, the ticket in a separate tool. muriki keeps customer, conversation and task tied together, with response times visible before they run out.

Get access
chamado #2481responder em 3h12
novo
em atendimento
resolvido
Cobrança duplicada
#2481 · há 12 min
AltaA fazer
Cobrança duplicada
#2481 · Marina respondeu
AltaEm andamento
Cobrança duplicada
#2481 · resolvido em 2h04
AltaConcluído
what changes in your support

Your customer never tells the story twice.

None of this is mandatory: each team takes what makes sense and ignores the rest. The module that delivers each item is marked — today only focus is standing.

work comes in here
01

From first conversation to close

  • Funnel stages

    projects

    See in ten seconds where every deal stopped.

  • Follow-ups with a date

    focus

    A promised call back becomes a dated commitment. No customer forgotten.

  • History per customer

    docs

    Whoever picks it up next already knows what was said. No “tell me again”.

Backlog12
MUR-33

Workspace onboarding

BacklogMediumMB
MUR-34

Search by subject

BacklogLowGT
This cycle5
MUR-24

Ship the early access

To doHighGT
MUR-36

Calendar MCP server

To doUrgentAL
In progress2
MUR-25

Offline sync with Yjs

In progressUrgentGT
MUR-28

Team invite by link

BlockedHighMB
Done8
MUR-27

The focus timeline

DoneMediumAL
the cycle board, with what sits in each column
02

When the ticket arrives

  • Tickets with response times

    projects

    The clock shows up before it runs out, not in next month's report.

  • Queue by priority

    projects

    Urgent rises on its own. Nobody has to babysit the queue.

  • Tickets open by link

    projects

    Your customer follows the ticket without creating an account or installing anything.

today's queue1 close to the deadline
Duplicate charge
#2481 · reply within 3h12
UrgenteEm andamento
Access for the new member
#2483 · reply within 6h
AltaA fazer
Question about the plan
#2479 · solved in 2h04
MédiaConcluído
the ticket queue, with the clock running
03

So the history is never lost

  • Written proposals

    docs

    The proposal you sent sits beside the deal, always in the right version.

  • Handover

    docs

    Holidays, team changes, someone leaving: the context stays, it doesn't walk out the door.

Decision: CRDT on the client

The document is the local source of truth. The migration is being handled inMUR-25Offline sync with Yjs— when it closes, the paragraph below stops being true.

architecturedecided on Jul 28
the written decision, with the task cited inside
and leaves here

What is ready lands where the team already is, with nobody copying links or telling people by hand.

  • Slackthe tightening deadline arrives before it runs out
  • Teamspeople in meetings don't miss the urgent one
  • Emailthe customer replies from where they already are
with the agent

What it does for a support team

  • The customer conversation becomes a ticket with due time, priority and owner.
  • A response time about to run out reaches Slack before it turns into a problem.
  • “How is this customer doing?” returns the whole history, from first contact to last ticket.
day to day

How the team uses it

  1. intake

    The request arrives by email, chat or link and joins the queue with a deadline.

  2. handling

    Whoever picks it up sees the customer history without leaving the screen.

  3. closing

    What was resolved stays recorded and feeds the next conversation.

Other use cases

Is your team in the next wave?

Access opens in waves, as the modules become ready. People on the list go first.

No spam. One email when early access opens.

I already have an account