Skip to main content

Use case

Billing and invoice questions by email

Keep invoices, VAT requests and payment questions with a visible owner while AI handles lookup and a person controls the final answer.

No card needed today.

Find the invoice behind the question

Dobrik points to the customer context behind each conversation
Find the invoice behind the question
  • Invoice question: The customer describes the charge or missing invoice.
  • Customer match: Check the relevant customer and company.
  • Connected billing record: Inspect permitted invoice and subscription information.
  • Team reply: Explain the result and the next step.

Give a specific answer while money-changing actions keep their required review.

Example: a teammate checks a connected payment record.

In the workflow

What changes once the work is visible.

  1. 01

    Route a VAT invoice request to the Billing Inbox and assign its owner.

  2. 02

    Check that an AI draft cites the current billing policy.

  3. 03

    Confirm a refund or payment dispute is held for human review.

A billing question, handled by the right person

A customer sends a receipt or asks to correct an invoice. Assign the conversation to the billing team and keep the account details and private notes with the request.

AI can help find relevant information and prepare a draft. Financial decisions and the final reply stay with a person.

Check order context and controlled commerce actions

Separate lookup from a financial decision

A billing conversation often mixes a simple question with a decision that changes money or account records. Let the team retrieve the current policy and order context quickly, then keep the approval or correction with the authorized person.

Test the boundary with a receipt request, a VAT correction and a refund dispute. The first may need a concise explanation; the last two need the right owner, evidence and an explicit decision.

Connect customer and order context

Show the evidence before changing a customer record

A billing reply can depend on the order, account identity, tax details or a previous promise. Keep the connected context available to the teammate, but do not treat a retrieved value as authorization to change it.

Ask the owner to verify the customer and the requested outcome before a correction, refund or account change. Record the decision in the conversation so the next handoff has a reason, not only a result.

Review connected customer context

Ground AI replies in approved knowledge

Give AI a clear source for support answers and keep review with your team before a reply reaches a customer.