Referrals become a repeatable commercial process when someone owns the request, the introduction, and the next step. Dots can help keep those stages connected without treating every satisfied customer as permission to contact their network.
This is a proposed workflow to configure and test with your business. It does not assume that Dots already has access to your sales systems.
Make introductions easy to request and easy to follow through
Define the result, the records the agent should use, and who owns the decisions. Keep the opportunity state in a shared tracker your team can inspect, with stable IDs, current sources, and the next action.
Prepare the information Dots needs
Relationship evidence
Completed work, customer feedback, active partnerships, and the responsible relationship owner.
Ideal referral
The problem you solve, suitable buyer types, geography, capacity, and exclusions.
Approved program
Any referral terms, incentive rules, eligible partners, and permitted messaging.
Pipeline records
Referrer, introduction date, permission, opportunity owner, next step, and verified outcome.
Verify app access before assigning work. Configure recurring tasks explicitly. Define action permissions before sending or changing records.
If a needed connection is unavailable, use an approved export for research and draft preparation. Keep source timestamps visible and require a current system check before an action depends on price, availability, or status.
Build the agentic workflow
1. Choose an appropriate moment
Use confirmed completed work or a documented positive experience. Avoid asking for introductions while an unresolved service issue still needs attention.
2. Prepare a specific request
Describe the kind of person or business you can help and why. Make it easy for the customer or partner to decide whether someone comes to mind.
3. Respect the introduction route
Draft a forwardable note or ask the referrer how they prefer to introduce you. Do not extract contacts from unrelated records and treat them as referred leads.
4. Own the handoff
When an introduction arrives, assign the opportunity and prepare a relevant response. Track the next agreed action so the referrer’s effort is not wasted.
5. Verify the outcome and acknowledge it
Reconcile the opportunity with actual sales and any program conditions. Prepare an appropriate thank-you without revealing confidential details of the new customer’s engagement.
A worked example
Illustrative scenario; this is not a reported customer result.
A customer offers to introduce a colleague after a completed project.
Dots prepares a short forwardable description of the service, records the introduction when it arrives, and prompts the relationship owner to arrange the next conversation.
A starter instruction for your dot
Review approved customer and partner records for suitable referral opportunities. Prepare specific requests and forwardable introductions for review. Do not contact third parties without an authorized introduction or other approved basis.
Track referrer, owner, next action, and verified sales. Use only approved referral terms and protect customer confidentiality.
For a repeating check, add a time, time zone, end date, and where results should arrive. Ask for confirmation that the schedule was saved. Define which exceptions deserve a notification and when the workflow should stop.
Measure the commercial result
Track requests, accepted introductions, qualified opportunities, won work, contribution, and referral costs. Deduplicate against existing leads so the same sale is not credited to several acquisition channels.
Keep the handoff clear
A referral is a relationship handoff, not just a name. Preserve the context and permission attached to the introduction, and leave new incentive arrangements or contractual promises to the business owner.
Begin with a small, reviewable pilot. Inspect the records and actual outcomes before expanding its scope. Give the agent enough authority to complete the agreed work, with clear ownership of exceptions.
Talk to Looski about this workflow. We can help map the data, integrations, decisions, and measurement before implementation.
Frequently asked questions
Can Dots ask all customers for referrals automatically?
Start with a defined eligible group, appropriate timing, and approved message scope. Resolve service issues first and make the intended introduction process clear.
How should referral revenue be attributed?
Record the referrer and introduction against a stable opportunity ID, reconcile with existing leads, and verify the resulting sale. Use a consistent attribution rule and report ambiguous cases separately.