Everything you need to know about Hyrre.
What makes Hyrre different from a chatbot or voice bot?
A chatbot answers a message. A voice bot completes a call. Hyrre runs the pipeline around those conversations. Its agents can contact people, capture structured information, apply outcomes, trigger messages or bookings, and pass the right work to your team—while every stage remains visible in one place.
What kinds of pipelines can Hyrre run?
Hyrre pipelines do not follow a fixed template. A pipeline might have two steps, five steps or twenty: contact someone, capture information, apply an outcome, send a follow-up, book an appointment, pause for human approval, and then continue. The structure depends on what you want to achieve, which steps Hyrre should handle, and where your people need to be involved. That same model can support recruitment, customer support, lead qualification, database cleaning, welcome calls and many other people-heavy operations.
Where does Hyrre end and my team begin?
There does not need to be one fixed handover point. Your people can review, approve or take over at any stage of the pipeline, then return the work to Hyrre for the next automated steps. You decide where automation makes sense and where judgement, relationships or accountability require a person.
What happens when a conversation needs a person?
Hyrre can pause the pipeline and hand the work to the right person with the conversation, summary and captured information attached. Once that person has reviewed it, made a decision or completed their step, the pipeline can continue from there. A human handover does not have to end the automation—it can be one stage within it.
How much control do we have over what the agents say and do?
You control the pipeline stage by stage: what each agent should do, what information it can use, what it should capture, which outcomes it can apply, and what happens next. You can add automated steps, human reviews, approvals, messages, bookings and conditional routes in whatever order the operation requires. Pipelines can change as your process changes.
Can Hyrre work with the systems we already use?
Hyrre is designed to sit alongside your existing systems rather than force you to replace them. Depending on the setup, data can move through direct integrations, APIs, or structured imports and exports. We map the full data flow before launch and clearly identify what connects directly and what requires custom work.
How long does it take to get a pipeline live?
A straightforward pipeline can usually be configured and tested within days. More complex implementations take longer when they involve several systems, detailed compliance requirements or multiple human handovers. We scope those dependencies upfront and test the complete pipeline before it handles live work.
How does Hyrre handle our data?
Hyrre is hosted in the UK, with data encrypted in transit and at rest. Access is controlled by organisation and user role, while payment information is handled separately by Stripe and never stored by Hyrre. Our security and privacy documentation explains our infrastructure, subprocessors, retention and UK GDPR safeguards in full.
How does pricing work?
Hyrre pricing is built around the pipeline you need rather than forcing every organisation into the same plan. Your package reflects expected usage, calling capacity, seats, enabled capabilities and billing interval. The included allowances and agreed price are set out clearly before launch, with payments and invoices handled through Stripe.