Sales Rules let workspace admins give Slokoto extra business guidance for how AI should reason about leads.
They are useful when your team has repeatable judgment patterns such as when to treat a lead as high intent, when to slow down, or when a conversation should be treated as effectively lost.
What it does
Sales Rules are added to the AI instructions used during:
- Todo reasoning
- Lead classification
- Pipeline stage suggestion
- Suggested next step and draft guidance
This means the AI can consider your business rules when deciding how to interpret a conversation.
What Sales Rules can influence
Sales Rules are best for telling the AI how to judge a situation.
They can influence:
- Urgency: whether something should feel urgent, routine, low priority, or not actionable yet
- Next step: what the rep should probably do next
- Draft guidance: how AI should frame a reply when the situation matches your rule
- Lead classification: whether something looks like a real sales opportunity or not
- Stage suggestion: whether a lead should stay active, move forward, or move toward Lost
In other words, Sales Rules work as a workspace playbook for AI judgment.
What Sales Rules do not do
Sales Rules are not a deterministic workflow engine.
They do not reliably:
- Count an exact number of follow-ups
- Check exact elapsed time conditions like "after 60 days"
- Send an email to a sales manager
- Assign a lead to a specific user
- Set arbitrary structured fields such as a custom lost reason
- Run backend workflows or scheduled automations
If you write a rule like:
If there is no reply for 60 days and we sent 5 follow-ups, move the lead to Lost, set reason to not responding, and email the sales manager.
the AI may understand the intent, but Slokoto does not currently execute those exact workflow actions automatically.
That kind of rule would require a dedicated automation engine with structured conditions and executable actions.
How to access it
- Go to Backoffice -> Settings.
- Open the Sales Rules tab.
- Review the starter example or add your own rules.
- Click Save Changes when you want the rules to become active.
Only workspace Admins can see and edit Sales Rules.
How to write a good rule
The best Sales Rules tell the AI how to interpret a conversation, not how to run a workflow.
Good rules usually:
- describe a recognizable sales situation
- explain the judgment you want the AI to make
- stay focused on prioritization, classification, or stage direction
- avoid exact counters, timers, or side effects
Better pattern
Use language like:
- "Treat this as high intent"
- "Keep this active unless a newer reply changes the picture"
- "Do not classify this as lost just because the message is short"
- "Move toward Lost when the customer explicitly declines"
Less effective pattern
Avoid trying to encode:
- exact time math
- exact follow-up counts
- notifications or emails
- field updates that the UI or backend does not explicitly support
Examples that work well
- If the customer asks for pricing, a quote, or availability, treat the lead as high intent.
- If the latest message says "follow up next month," lower urgency until that timeframe approaches.
- If a returning customer reaches out, do not classify them as low priority just because the message is short.
- If the lead mentions procurement, legal review, or internal approval, keep the opportunity active rather than treating it as cold.
- If the sender is clearly trying to sell to us, classify the thread as not a lead.
- If the customer explicitly says they chose another vendor, treat the opportunity as Lost unless a newer message reopens the deal.
Examples that do not fit this feature
- After exactly 5 follow-ups and 60 days with no reply, send an email to the sales manager.
- If deal value is above $10,000, assign the lead to John.
- If there is no response for 21 days, set lost reason to not responding and notify finance.
- If the CRM field "territory" equals East and the last call outcome is voicemail, trigger a workflow.
These are automation rules, not AI judgment rules.
Built-in starter example
When your workspace has no saved Sales Rules yet, Slokoto shows one starter example in the Sales Rules tab:
If a lead explicitly says they are not moving forward or chose another vendor, classify the opportunity as Lost unless a newer message reopens the conversation.
Why this is a good starter rule:
- it describes a clear conversation signal
- it affects stage direction, which the AI already supports
- it avoids exact counters and timers
- it avoids promising actions the product cannot execute automatically
The starter example is not saved automatically. It only becomes active after you click Save Changes.
Tips / Best practices
- Start with 1 to 3 high-signal rules instead of writing a long policy document.
- Prefer rules about judgment instead of rules about automation.
- Write rules in plain business language, not pseudo-code.
- Review results in Todo and Pipeline after saving new rules.
- If a rule is too broad, narrow the wording so the AI applies it only in the intended cases.
- Use disabled rules as drafts while deciding what should go live.
Frequently Asked Questions
Q: Can Sales Rules send emails or notify managers automatically?
No. Sales Rules guide AI reasoning, but they do not run backend workflows or send emails.
Q: Can Sales Rules move a lead to Lost?
They can influence the AI to treat a lead as Lost or suggest a Lost stage when the conversation supports it. They do not act like a guaranteed automation engine.
Q: Can I use exact rules like "5 follow-ups" or "60 days"?
You can write them, but Slokoto does not currently evaluate those exact conditions deterministically. Write those rules as judgment guidance instead of exact workflow logic.
Q: Who can edit Sales Rules?
Only Admins.
Q: Are Sales Rules immediately active when I type them?
No. They become active only after you click Save Changes.
Q: Should I write a lot of rules?
Usually no. A short set of clear, high-signal rules works better than a long list of overlapping instructions.