Automation that handles your follow-up. Tell dot, or click it together.
A task when a quote sits for a week, a reminder the day before the appointment, a status that moves on by itself. Rules read like plain sentences and keep running in the background.
When a record has sat in Quote sent for 7 days
create a task Call the customer
Follow‑up that does not get forgotten.Not even when it is busy.
A rule is one sentence: when this happens, do that. stipt keeps track of when the moment comes.
Rules
Rules that read like a sentence.
Every rule sits under the moment it works on: when a record reaches Approved, when a quote has been open for seven days, one day before an appointment. You see what the rule does then, how often it happened, and one switch turns it on or off.
- Send an email or WhatsApp, create a task or set a status
- Only for certain record types, appointment types or sources
- Pause with the switch, without deleting anything
With dot
Describe it, dot sets it up.
Type what you want in plain language, for example: after a no‑show, send a WhatsApp to reschedule. dot finds the template, the status and the appointment type and shows the rule as a card. It is only created once you confirm.
- dot uses your own templates and statuses
- Nothing happens without your click
- Workflows are set up by dot as a draft that is switched off
On time
Reminders at the right moment.
Time rules count in working days if you want, based on your own opening hours, and go out at a fixed time. A quote sent on Friday gets a reminder after three working days: Wednesday at 09:00. If a customer books in the meantime, the reminder for their scheduling link drops by itself.
- Working days or calendar days, per rule
- A fixed time of day, never in the middle of the night
- A heads‑up when a status stays unchanged too long
Log
You see what happened, and why.
Every time a rule is evaluated, it goes in the log: carried out, no match or limit reached, with the reason in plain language. On your start page one line tells you whether sending and automation went well over the last 24 hours.
- Every run with its outcome and the reason in plain language
- Rules that keep triggering each other are stopped
- Ask dot to rerun a workflow that got stuck
Small rules, a lot less work.With guardrails on.
You see what a rule will do before it does it. And it does not do it twice.
Try it first
Pick a recent record and see what the rule would do right now, with the real names.
Never twice
A rule that emails or sends a WhatsApp won't keep sending the same message. You set how often per rule.
Status after delivery
Once the email or WhatsApp is delivered, the record moves on to the status you pick.
Distribute by workload
A new conversation goes automatically to a team member who has room for it.
Escalate in the inbox
If a conversation is left waiting too long, the right colleague gets a heads‑up.
Tasks from a template
A rule creates a task with title, owner, deadline and subtasks in one go.
Fixed attachments
Attach your terms or a brochure to an email template. They go with every email, also when a rule sends it.
Everything in one place
Every moment also shows the steps set up on an appointment type or form.
You manage rules, workflows and templates in Studio. Studio comes with every seat at no extra cost; you set per person who builds there under Rights. See pricing
Workflows for the rest.When a rule is not enough.
For branches, waiting times, your own code and other systems there is the workflow builder in Studio. You connect blocks on a canvas, test them straight away and publish once it works.
- Start on a webhook, a schedule, an email or something in stipt
- HTTP requests to any API, your own JavaScript and other systems
- Every run saved, with what went in and came out per block
Frequently asked questionsAbout automation.
Do I need technical knowledge?
No. You build rules with drop‑down choices, or you describe to dot what you want and confirm its proposal. The workflow builder with code and webhooks is there for those who want more, but you do not need it for day‑to‑day work.
Is Studio included in my subscription?
Yes. Studio comes with every Admin and User seat at no extra cost. Admins always have access; a User builds and manages rules, workflows and templates with the Studio right, which an admin sets per person. The rules themselves simply run for the whole company.
Can a rule send too many messages by accident?
There are guardrails. A rule that emails or sends a WhatsApp does not keep sending a customer the same message, and you set per rule how often it may run. Rules that keep triggering each other in a loop are stopped automatically, and the log shows every run.
Does automation also work for leads that come in through the API?
Yes. A record that is created or changes status through the API runs through the same rules as a change in the app. A lead from an integration gets the same follow‑up as a lead a colleague types in.
What is the difference between a rule and a workflow?
A rule is one trigger with conditions and one or more actions in a row: when this happens, do that. A workflow is built on a canvas, for branches, waiting times, your own code, requests to other systems or calling another workflow.
What happens when a workflow fails?
Every run is in the history, with what went in and came out at each step. You can ask dot to rerun a failed run. With incoming webhooks, too, nothing is lost when something goes wrong.
From the knowledge base
See which follow‑up you can automate?
Bring your list of what keeps getting left behind. In the demo we show which rules pick it up for you.