If a business has an internet connection (of course they do), then they have the ability to host a website just as much as they have the ability to answer the phone. The same software/provider relationship that would provide AI answering service could easily facilitate online interaction. So if oblivous AI enduser points an AI agent at a business with AI agent answering, then the answering agent should be ‘If you are an agent, go to shorturl.at/JtWMA for chat api endpoint’, which may then further offer direct options for direct access to the APIs that the agent would front end for a human client, instead of going old school acoustic coupled modem. The same service that can provide a chat agent can provide a cookie cutter web experience for the relevant industry, maybe with light branding, providing things like a calendar view into a reservation system, which may be much more to the point than trying to chat your way back and forth about scheduling options.
then they have the ability to host a website just as much as they have the ability to answer the phone
Many people in the developed world are behind CGNAT. Paying for an Ipv4 is a premium, and most businesses either setup shop on an existing listing page (e.g. facebook), or host a website from website provider/generator.
A phone number is public, accessible, and an AI can get realtime info from a scrawled in entry in a logbook using OCR
So for one, business lines almost always have public IPv4. Even then, there are a myriad of providers that provide a solution even behind NAT (also, they probably have public IPv6 space). Any technology provider that could provide AI chat over telephony could also take care of the data connectivity path on their behalf. Anyone that would want to self-host such a solution would certainly have inbound data connectivity also solved. I just don’t see a scenario where a business can have AI telephony but somehow can’t have inbound data access.
So you have a camera on a logbook to get the human input, but then that logbook can’t be a source of truth because the computer won’t write in it and the computer can take bookings. I don’t think humans really want to do a handwritten logbook anyway, a computer or tablet ui is going to be much faster anyway.
If a business has an internet connection (of course they do), then they have the ability to host a website just as much as they have the ability to answer the phone. The same software/provider relationship that would provide AI answering service could easily facilitate online interaction. So if oblivous AI enduser points an AI agent at a business with AI agent answering, then the answering agent should be ‘If you are an agent, go to shorturl.at/JtWMA for chat api endpoint’, which may then further offer direct options for direct access to the APIs that the agent would front end for a human client, instead of going old school acoustic coupled modem. The same service that can provide a chat agent can provide a cookie cutter web experience for the relevant industry, maybe with light branding, providing things like a calendar view into a reservation system, which may be much more to the point than trying to chat your way back and forth about scheduling options.
Many people in the developed world are behind CGNAT. Paying for an Ipv4 is a premium, and most businesses either setup shop on an existing listing page (e.g. facebook), or host a website from website provider/generator.
A phone number is public, accessible, and an AI can get realtime info from a scrawled in entry in a logbook using OCR
So for one, business lines almost always have public IPv4. Even then, there are a myriad of providers that provide a solution even behind NAT (also, they probably have public IPv6 space). Any technology provider that could provide AI chat over telephony could also take care of the data connectivity path on their behalf. Anyone that would want to self-host such a solution would certainly have inbound data connectivity also solved. I just don’t see a scenario where a business can have AI telephony but somehow can’t have inbound data access.
So you have a camera on a logbook to get the human input, but then that logbook can’t be a source of truth because the computer won’t write in it and the computer can take bookings. I don’t think humans really want to do a handwritten logbook anyway, a computer or tablet ui is going to be much faster anyway.