A nearby office is only a useful catering prospect if your restaurant can serve its group size, delivery window, budget, and ordering process. Give Dots that qualification job before asking it to collect names.
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.
Build a qualified catering pipeline
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
Service limits
Delivery area, lead time, maximum orders per service, setup requirements, and days you can accept additional work.
Sellable packages
Current menus, minimum order, per-person pricing, fees, and chef-approved dietary information.
Prospect evidence
Public company websites and verified business contacts, with the source and date recorded for every claim.
Existing relationships
Current accounts, prior inquiries, owner assignments, and records of people who should not be contacted.
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. Define the ideal order
Choose a concrete target such as weekday team lunches within your delivery zone. Rank prospects by operational fit, rather than the number of email addresses found.
2. Research the account
Have Dots capture location, a relevant office or events contact, and evidence of a possible use case. A company size estimate is a hypothesis, not a confirmed headcount.
3. Prepare a relevant approach
Match one approved package to the potential occasion. Explain why it may fit and ask a simple qualifying question. Review the recipient and message before the first campaign.
4. Work the replies
Record date, group size, budget, dietary requests, and delivery details. Route missing information back to the prospect; route menu or price exceptions to staff.
5. Advance or close the opportunity
When qualified, prepare a quote for approval. Mark declines and completed orders promptly so a scheduled follow-up cannot continue after the conversation has ended.
A worked example
Illustrative scenario; this is not a reported customer result.
An office asks about lunch for 24 people next Thursday. Dots checks your lead time and delivery area, identifies two approved menu options, and requests the delivery window. Staff confirms capacity before a quote is issued.
A starter instruction for your dot
Research ten potential office catering accounts within our approved delivery area. Use the attached menu, service limits, and existing account list. Record source links and unknowns.
Prepare a relevant first message for each qualified account; do not send it. Track replies we supply and propose the next action. Ask staff to confirm capacity and any pricing exceptions.
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 researched accounts, qualified conversations, quotes, paid orders, and repeat orders separately. Calculate contribution after food, labor, delivery, and campaign costs; a large order can still be a poor fit.
Keep the handoff clear
Keep capacity confirmation with the restaurant. Public research cannot establish a prospect’s budget or permission to purchase, and the agent should label those fields unknown until the buyer supplies them.
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 find the catering buyer at every company?
No. It can investigate public information and connected records. Where a buyer cannot be verified, keep the role or contact unknown and use an appropriate general business inquiry.
Should outreach be fully automated immediately?
Start with reviewed recipients and messages. Expand to a specifically authorized campaign only after testing the contact data, reply handling, exclusions, and stop conditions.