In “Services”, Elbuz runs a sale as a deal from request to payment, makes a person a customer from the first paid invoice and flags renewals due, based on past payments.
When you need this:
- A customer asked about a demo or plans — “Pulse” suggests a deal with the stages New → Qualification → Proposal → Contract → Payment.
- Monthly subscription — 7 days before the expected payment, “Pulse” suggests a reminder.
- A customer stopped paying — after two missed intervals, they're “Dormant”.
- An outage report came in — AI sets a high-priority task and drafts a reply.
Where to start: choose “Services” in your company details.
What the “Services” format does
- A deal board with service stages — deals are on from the start, with a forecast based on stage probability.
- A purchase is a paid invoice or a posted certificate of completion — an invoice and a certificate for the same work count once.
- Stages based on payment rhythm — “Dormant” is calculated from the customer's own interval.
- Renewal reminders — every day, “Pulse” suggests a follow-up for those whose payment is coming up.
- Request types for service businesses — support, bugs, billing, account access.
How to run a deal from request to payment
In “Services”, deals are on from the start. The deal board gets the format's stages — if it has no deals yet and you haven't changed the stages (name, order, probability):
New (10%) → Qualification (30%) → Proposal (50%) → Contract (70%) → Payment (90%) → Won / Lost
The percentage is the chance that a deal at this stage closes; the forecast in the “Pipelines and stages” window is based on it. You change a stage's probability, name and order there, and the “Open deals” button takes you to the board itself. The “Negotiation” stage is off in services: “Qualification” and “Proposal” cover the conversations.
A manager or “Pulse” runs the deal. For an email or chat of the “Consultation” type — a pre-sale question, a demo, a plan comparison — “Pulse” suggests a deal, and when the customer agrees or promises to pay, it suggests the next stage. A won deal doesn't create an invoice itself: create it from the deal with “Based on”.
What counts as a payment
Services have no customer order with delivery. Elbuz counts one of two documents as a purchase:
- an invoice with the payment status “Paid”;
- a certificate of completion that is posted (signed).
The main document is the paid invoice.
- A certificate counts as a separate purchase only if the customer has no paid invoices and the certificate wasn't created “based on” another document. So an invoice and a certificate for the same work are one purchase, and “Regular” means a second payment.
- Not counted: canceled documents and returns.
- An invoice not marked as paid doesn't count, even if the money arrived: set the payment status, or the customer stays a lead.
The format doesn't set its own status sequence for customer orders: if you use them, they follow the shared document pipeline.
When a customer becomes regular or dormant
The stages are the same as in other formats, but the rules suit regular payments:
| Stage | When |
|---|---|
| Lead | got in touch but hasn't paid yet |
| Qualified | a manager confirmed interest, or a deal is open for them |
| Customer | first payment, a posted certificate of completion, or a won deal |
| Regular | second payment and on — the customer renews |
| Dormant | hasn't paid for two of their usual intervals, but not sooner than 45 days |
| Lost | over a year without a payment |
| Not a fit | set by a manager |
Elbuz calculates the “usual interval” per customer: the time between the first and last payment divided by the number of gaps. A monthly subscriber becomes “Dormant” after about 60 days without paying; a quarterly payer, after about 180. With one payment, the minimum applies — 45 days. There's no separate “paid until” field: Elbuz goes only by payment dates.
How not to miss a renewal
The “Service renewal” process turns on with the format. Daily at 9:00, it finds customers whose next payment is expected within 7 days and who have no planned follow-up, and suggests in “Pulse” a “Remind about the service renewal” follow-up for the owner. Up to 30 customers per run. It doesn't issue the renewal invoice — a person does.
“Expected” uses the same interval: the last payment plus the customer's usual gap. So the process only sees those who paid at least twice: one payment gives no interval. You can change 7 and 30 on the process card on the “Automations” tab of “Pulse”; changing the business format still turns such a process on and off.
How to rewrite the rule in words. In the AI consultant chat, write, for example:
- “in the Service renewal process, remind 10 days ahead instead of 7”;
- “find customers whose next payment is due in a week or sooner and who have no planned follow-up, and every day suggest a renewal reminder”.
The consultant explains the change and shows a “Change the process “…”” or “Create the process “…”” button; nothing is saved until you click it. By default, only “Management” can do this (create a workflow in words).
A change made through the consultant rewrites the process schema, and after that the business format no longer switches this process. To change only the number of days, edit the number on the process card.
How to leave it to AI. On the “Trust” tab of “Pulse”, turn on “Act on its own” for “Plan a follow-up” — renewal reminders go into the owner's calendar without your click; undo them on the “Done by AI” tab. By default only “Management” has this switch; it's company-wide and covers all follow-ups, not just this process.
A new customer with one payment won't get a reminder yet. Schedule a follow-up for the renewal date manually — in the customer card, with the “Schedule” button (next follow-up).
How AI sorts requests: support, bugs, billing
In the “Services” format, AI sorts emails and chats into a different set of request types than for stores. The type decides what “Pulse” suggests and whether AI can reply on its own:
| Type | What “Pulse” suggests | Reply without a person |
|---|---|---|
| Support | a draft reply from your knowledge base articles | yes, if trusted |
| Bug | a high-priority task | no, always reviewed |
| Billing | a draft reply | no, always reviewed |
| Account access | a draft reply without passwords or links | no, always reviewed |
| Feature request | a task | yes, if trusted |
| Consultation | create a deal | yes, if trusted |
For a question about a service in an email or chat, “Pulse” suggests the “Arrange a consultation or a meeting” follow-up if the customer has no planned follow-up yet. How trust works and why some replies always go to a person — see “Customer replies”.
Phrases for the AI consultant:
- “which customers have a payment expected this week?”
- “show dormant customers who used to pay monthly”
- “which deals have been at the Proposal stage for more than a week?”
- “what do people write to support about most often?”
Scenarios
Website request → paid contract
What to do. Someone wrote about a demo — “Pulse” suggested creating a deal, and you accepted. Move the deal through the stages: “Qualification” after the call, “Proposal” after the quote, “Contract”, “Payment”. Issue the invoice from the deal with the “Based on” button.
What you get. Once the deal opened, the lead became “Qualified”. When the invoice is marked “Paid”, the person becomes a “Customer” at the hourly recalculation.
What won't happen. Moving the deal to the “Payment” stage doesn't make them a customer: you need a paid invoice or the deal in “Won”.
Monthly subscription: don't miss the renewal
What to do. Mark monthly invoices as paid.
What you get. From the second payment, the customer is “Regular”, and 7 days before the next expected payment “Pulse” suggests a renewal reminder. Two months without paying — the stage is “Dormant”, and the customer shows up in the “Dormant customers” tile in “Contacts”.
A customer reported an outage
What to do. Nothing in advance: AI tags the email with the “Bug” type.
What you get. A high-priority task and a draft reply appear in “Pulse”. AI won't send the reply on its own even if trusted — a person reviews it.
FAQ
The customer paid, but the stage is still “Lead”. Why?
Most often the invoice doesn't have the payment status “Paid”. Set it, and within an hour Elbuz moves the person to “Customer”. A posted certificate of completion also counts.
Can I set our subscription to be yearly instead of using the interval?
No, there's no separate subscription term: Elbuz uses the average gap between the customer's own payments. For a yearly subscription, this means the customer never becomes “Dormant”: after a year without a payment, they go straight to “Lost”.
Why is there no “Negotiation” stage?
In the services set, “Qualification” and “Proposal” replace it. The stage isn't deleted: it's off, and you can turn it on in the “Pipelines and stages” window if you need it.
Why didn't all customers get a renewal reminder?
The process only picks customers who paid twice or more, whose next payment is expected within 7 days, and who have no planned follow-up. Up to 30 customers per run.
We sell both services and products. Which format should we choose?
The one that brings in most of your revenue. If it's products, choose a store format and turn on “Track deals” for service contracts. Then orders make a person a customer, and paid service invoices don't affect the stage.
Where it is and who has access
- Menu
- “Deals”, “Pipelines and stages”, “Invoices” in the “Orders” workspace
- Access right
- “Deals” and documents; only “Management” can change “Pulse” processes
- Prepare
- the “Services” format in your company details
Related topics
- For an overview of all four formats — Business format: what it changes.
- If a deal is at “Contract” but the customer is still a “Lead” — Customer stage and deal stages.
- To find deals and invoices in a workspace — The “Deals” workspace.
- To change the schedule or conditions of reminders — CRM automations.
