The website reader behind SaaSyVoice AI receptionists
SaaSyVoiceBot reads a business's website so its SaaSyVoice AI phone agent knows the services, prices, hours and contact details callers ask about. It only visits a site when that business, or someone setting up its AI receptionist, asks us to read it.
The user agent always contains SaaSyVoiceBot/1.0. The full string is:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 (compatible; SaaSyVoiceBot/1.0; +https://saasyvoice.ai/bot)
Requests come from Google Cloud.
Some website security tools turn away every automated reader. If SaaSyVoice told you your site blocked it, here is what to change. Menu names move around between versions, so if a step doesn't match what you see, ask your web person or your host.
Add a WAF custom rule (under Security) that matches User Agent contains SaaSyVoiceBot with the action Skip. If you use Cloudflare's free Bot Fight Mode, a rule can't bypass it: turn it off, or use one of the alternatives below instead.
Check Wordfence's firewall settings (rate limiting and blocking) for a rule that blocks crawlers or this user agent, and add an exception for SaaSyVoiceBot. If you're not sure where, your host or Wordfence support can do it.
In the Sucuri firewall dashboard, look for the access control or allowlist settings and allow the SaaSyVoiceBot user agent, or ask Sucuri support to.
On SiteGround, Bluehost, GoDaddy, Hostinger and similar hosts, the block is often a host-level bot filter. Ask their support to allow the SaaSyVoiceBot user agent on your site.
You don't have to. In the SaaSyVoice setup chat you can:
Add this to your robots.txt and SaaSyVoiceBot stops reading pages it finds on its own:
User-agent: SaaSyVoiceBot Disallow: /
A page someone specifically asks us to read is still fetched once, the way other on-request readers work. To turn it away completely, block the SaaSyVoiceBot user agent in your firewall.