Automated TextNow Callback Scheduling
Every morning, WebRun opens TextNow, reads the conversations from overnight, picks out the missed calls and text messages that clearly need a human call back, books each one a free slot in Google Calendar, and posts Microsoft Teams a list naming the owner, the contact and the booked time.
How do I turn missed calls and texts into scheduled callbacks?
WebRun reads your TextNow conversations every morning and picks out the missed calls and messages that need a human call back. It books each one a free slot in Google Calendar and posts Microsoft Teams a list naming the owner, the contact and the time, so a missed call becomes a scheduled conversation.
- Every conversation needing a call has an owner and a booked time by 8:30 AM
- Urgent threads land in the earliest free slot of the day
- Callbacks that could not be booked are flagged instead of dropped
Built for small business owners · service businesses · sales teams · support teams
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.textnow.comin a real browser with your saved login - no setup, no API keys. -
1
TextNow - find conversations needing a callback
textnow.com
WebRun opens TextNow to find conversations needing a callback. - Open TextNow and read the conversations since the last run
- Capture missed calls and unanswered text messages with the contact and phone number
- Read the last few messages in each thread to judge whether it needs a call rather than a reply
- Set aside spam, automated notices and threads already answered by a teammate
- Note anything that reads urgent so it can be booked earliest
Done when Every conversation needing a callback is captured with its contact and context.
-
2
Google Calendar - book the callback slot
calendar.google.com
WebRun opens Google Calendar to book the callback slot. - Find the next free slot on the right teammate's calendar for each callback
- Create a short event titled with the contact name and phone number
- Put the last message and the reason for the call in the event description
- Book the urgent ones into the earliest slots and keep the rest inside working hours
Done when Every callback has a real time slot on a real calendar.
-
3
Microsoft Teams - name the owner
microsoft.com
WebRun opens Microsoft Teams to name the owner. - Post the team channel a list of today's callbacks with the owner named against each one
- Show the contact, the booked time and one line of why they need calling
- Flag anything that could not be booked because a calendar was full so a human can move it
Done when Every callback has a named owner and a slot posted in Microsoft Teams.
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 text or call the contact itself?
No. WebRun only reads TextNow. It never sends a text, never places a call, and never replies in a thread. The call itself is always made by the teammate named on the assignment.
Does the calendar invite go to the contact?
No. The event is created on your teammate's own calendar with no external guests, so it works as an internal reminder. The contact is never invited and never notified.
How does it decide a message needs a call rather than a reply?
It reads the last few messages in the thread and looks for a missed call, a question left unanswered, or wording that reads urgent. Anything ambiguous is listed for a human to judge rather than booked.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.