Route new calibration service enquiries to the right person fast
Every hour, WebRun reads new calibration enquiry emails in Gmail, extracts the instrument type, urgency, and customer details, logs each lead in a Google Sheet, checks IndySoft for existing customer records, and routes the enquiry to the right technician or rep in Slack.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically route incoming calibration service enquiries to the right technician?
WebRun reads every new calibration enquiry in Gmail each hour, extracts the instrument type and customer details, checks IndySoft for existing customer history, logs the lead in Google Sheets, and routes it to the right technician in Slack, so inbound service requests reach the right person within minutes of arriving.
- New enquiries reach the right technician within minutes, not hours
- Returning customers are identified before the first call back
- Every inbound lead is logged and tracked from first contact
Built for calibration lab managers · commercial calibration services · metrology sales teams · quality lab administrators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
mail.google.comin a real browser with your saved login - no setup, no API keys. -
1
Gmail - read new enquiry emails
WebRun opens Gmail to read new enquiry emails. - Open Gmail and find unread emails tagged as calibration enquiries in the last hour
- Extract the sender name, email, company, instrument description, and any urgency signals
- Mark each email as processed with a label to avoid re-reading
Done when All new enquiry emails are read and their details extracted.
-
2
IndySoft - check for existing customer record
WebRun opens IndySoft to check for existing customer record. - Search IndySoft for an existing customer record matching the sender's company or email
- Note whether this is a returning customer or a new prospect
- Capture any existing asset history relevant to the enquiry
Done when Each enquiry is marked as returning customer or new prospect with relevant history noted.
-
3
Google Sheets - log the lead with extracted details
WebRun opens Google Sheets to log the lead with extracted details. - Append a new row for each lead with date, customer, instrument type, urgency, and returning or new status
- Add a column for the assigned technician to be filled after routing
Done when The lead log is updated with every new inbound enquiry.
-
4
Slack - route to the right technician or rep
WebRun opens Slack to route to the right technician or rep. - Post a routing message to the lab-intake Slack channel naming the enquiry, instrument type, and customer status
- Tag the technician or rep best suited to the instrument type based on your routing rules
- Include the Google Sheets row link for quick access
Done when Every new enquiry is routed to the right person in Slack with full context.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it reply to the enquiry automatically?
No. WebRun only reads, logs, and routes the enquiry internally. Any reply to the customer is drafted separately or sent by your team directly.
How does it decide who to route to in Slack?
It matches the instrument type from the email against your routing rules, which you set up once when configuring the workflow.
What if the customer already has a record in IndySoft?
It checks IndySoft first and flags returning customers in the Slack message and Google Sheet, so your team can see prior asset history immediately.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.