Product
Routines
Routines are event-triggered automations. Every inbound event — a new DM, a missed call, a form submission, a new contact, an after-hours call — can fire a routine that qualifies, routes, notifies, or responds. Build the rules once; Whitmore runs them forever. This is the differentiator vs. dumb AI answering services that only handle the conversation.
Why businesses choose this
Automate the repetitive decisions your team makes 20 times a day
Consistent execution 24/7 — no human needed for routine routing
Reduce manual handoffs between channels and team members
Build once, run forever — no rebuilding workflows month over month
Debug without breaking production — test-run mode catches errors early
How It Works
When [X] happens, Whitmore does [Y] — automatically
Event catalog across all channels
Triggers include: new DM (Facebook, Instagram), missed call, call completed, new contact created, form submitted, after-hours call, appointment booked, appointment cancelled, and more.
Conditional logic with branching
Routines support if/then branching — "if the caller mentioned emergency, route to on-call; otherwise, book a callback." Build the decision tree your team runs manually today.
Reusable templates
Start from a template for common patterns — missed-call recovery, new DM qualification, after-hours response — and customize from there. No starting from scratch.
Test-run mode for debugging
Simulate a trigger and trace exactly what Whitmore would do before going live. Catch logic errors without affecting real contacts.
Full audit log
Every routine execution is logged — what triggered it, what happened at each step, what the outcome was. Investigate any contact's history in one click.
AI-native step execution
Steps can include AI actions — drafting a personalized reply, qualifying a lead, summarizing a call — not just mechanical if/then logic.
Industries that benefit most
This product works especially well for these industries — but if you don't see yours, we probably still have you covered.
FAQ
Common questions about Routines
What events can trigger a Routine?
The current trigger catalog includes: new inbound DM (Facebook or Instagram), missed call, call completed, new contact created, contact field updated, form submitted, appointment booked, appointment cancelled, and after-hours call. The catalog expands with each platform release.
How deep can the conditional logic go?
Routines support branching up to several levels deep — for example: trigger on missed call → check if after-hours → if yes, send SMS; if emergency keyword was detected, also alert on-call. For very complex decision trees, we can help design the logic during onboarding.
How do I debug a Routine that isn't behaving as expected?
Use test-run mode to simulate any trigger event. Whitmore traces every step and shows you exactly what decision was made at each branch. You can also review the audit log for any real execution to see what happened.
What happens if a Routine step fails — does it retry?
Yes. Transient failures (network errors, calendar unavailability) trigger automatic retries with exponential backoff. If a step repeatedly fails, you get a notification and the routine is flagged for review in the audit log.
Can Routines connect to external tools and APIs?
Yes. Routines can send webhook payloads to any external system — HubSpot, Salesforce, Slack, or a custom API endpoint. This lets you trigger actions in your existing stack based on Whitmore events.
Are Routines included in the base plan or a separate add-on?
Routines are included as a core capability in Whitmore — not a workflow automation add-on that costs extra. Book a demo for exact pricing based on your plan.
Make your operation run itself
30-minute demo — we'll build a routine live with you on the call.
Book a Demo