Automated Amtelco Client Script Update Drafts
When a client submits a script or greeting change request, WebRun opens their account in Amtelco, drafts the new wording as a pending update, logs the request to Google Sheets for audit, drafts a confirmation email in Gmail, and posts the pending draft to Slack for a supervisor to review before anything goes live or gets sent.
How do I safely draft client script updates without publishing them live?
When a client submits a script or greeting change request, WebRun opens their Amtelco account, drafts the new wording as a pending update, and logs the request to Google Sheets for audit. It drafts a confirmation email in Gmail and posts the pending draft to Slack, leaving both the live script and the client email unsent until a supervisor reviews and approves them.
- No script or greeting change reaches a live call before a supervisor approves it
- Every request is logged with the old and new wording for a clean audit trail
- Clients get a clear confirmation draft instead of a verbal promise nobody wrote down
Built for answering services · virtual receptionist companies · medical answering services · legal intake answering services
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
www.amtelco.comin a real browser with your saved login - no setup, no API keys. -
1
Amtelco - open the client account and current script
amtelco.com
WebRun opens Amtelco to open the client account and current script. - Open the client's account in Amtelco and read the current greeting or script text
- Draft the requested wording as a pending update. Do not publish it to the live call queue
- Note exactly what changed compared to the current live version
Done when A pending script draft exists in the client's account, separate from the live version.
-
2
Google Sheets - log the change request for audit
google.com
WebRun opens Google Sheets to log the change request for audit. - Log the request with the client, the date, who asked for it, and the old and new wording
Done when The change request is recorded in the audit log.
-
3
Gmail - draft the client confirmation email
gmail.com
WebRun opens Gmail to draft the client confirmation email. - Draft a confirmation email to the client summarizing the new wording exactly as requested
- Save it as a draft and leave it unsent
Done when A confirmation draft sits ready in Gmail, unsent.
-
4
Slack - send the draft for supervisor approval
slack.com
WebRun opens Slack to send the draft for supervisor approval. - Post the pending script draft and the confirmation email to the supervisor for review
- Ask the supervisor to approve before the script is published live or the email is sent
Done when A supervisor has been asked to approve the draft before anything goes live.
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
Will it publish the new script to the live queue on its own?
No. WebRun only drafts the update as a pending change inside Amtelco. A supervisor has to approve it before it ever reaches the agents answering live calls.
Will it email the client without anyone checking?
No. The confirmation email is drafted in Gmail and left unsent. It only goes out once a supervisor reviews and sends it.
Why log the request separately from the draft?
The Google Sheets log keeps a plain audit trail of who asked for what and when, so you can trace every script change even after it has been approved and published.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.