Frequently asked questions

IHS Flow is a managed AI agent service from Infotech Houston Solutions. We design, host and run AI agents that complete business workflows — answering calls, working inboxes, updating EHR and business systems and running SOPs — on our secure platform.

Most first workflows go live within one to three weeks after the workflow analysis, including a trial period in Assisted mode.

No. We believe results should speak for themselves. Start with a free workflow analysis and one workflow.

No. Agents work with the systems you already use — through APIs, OAuth connectors or browser automation.

Pricing is based on the workflows, channels and volume involved. After the free analysis you receive a clear monthly proposal with usage visibility in the portal.

Each agent has a role, instructions, tools and permissions. Depending on the workflow it can talk on the phone, send and read email, text, operate web applications, read documents and faxes, update systems and run scheduled tasks.

We choose per agent from leading models, including Anthropic Claude and OpenAI, balancing accuracy, speed and cost. For voice we use multiple speech engines, including an option that transcribes on our own servers.

Yes. IHS owns its dial tone and network, so agents register as phone extensions for inbound and outbound calls, transfers, DTMF and after-hours rules.

Yes. Your team can log in to the client portal to see dashboards, task history, insights, alerts and the full audit log for your organization.

It follows your escalation rules — asking a person for approval, transferring a call or routing the item to a queue with a summary.

IHS Flow is operated under IHS’s HIPAA program and SOC 2 Type II controls, and we sign a Business Associate Agreement with healthcare clients before processing PHI.

On IHS-owned infrastructure in Houston and Dallas, Texas datacenters.

No. Your data is not used to train public AI models, and PHI workloads use providers under BAA and zero-retention terms.

Call recordings are off by default. We keep encrypted transcripts and summaries instead; recordings can be enabled where your policy requires them.