Scheduled call
Useful when a conversation needs preparation and a reserved time. Availability and confirmations should match the person who will actually call back.
Fix the handoff after an inquiry.
We map where a request arrives, who owns it, and what happens next. Then we scope the routing, follow-up, and tools your team can support.
Choose a response path your team can support.
Start with where inquiries stall, who will answer, and what should happen if they cannot. More channels do not automatically mean better service.
Written request
Useful when the prospect needs to explain the work. Ask for the relevant details, record the request, and assign a person to review it.
Direct phone
Useful for time-sensitive contact when someone can answer or return calls. Hours, overflow, and missed-call handling must be practical for the business.
Automated phone or chat
Consider it for repeatable questions or structured intake only when disclosure, approved answers, testing, and a human escalation route are defined.
Our own intake uses two paths.
The Solurnis booking page offers a scheduled phone call or a written request. A person handles the next conversation.
What is automated, and what stays with a person?
The written form validates the required details and sends the request for storage. Confirmation and internal email delivery are attempted; delivery is not guaranteed by the success screen. A person reviews the request and decides how to respond.
The call option opens Cal.com availability. It does not turn a written request into a booking or decide the project scope.
Book a phone call
Select an available 20-minute time, provide a callback number, and Solurnis calls you. The scheduling experience is provided through Cal.com.
View available timesSend project details
A written request is recorded for review. Confirmation and internal email notifications are attempted; a person handles the reply.
Send a written requestSet limits before adding an agent.
An agent may answer approved questions, collect structured details, or offer a next step. Whether it fits depends on the caller, the information involved, and the cost of a wrong answer.
- What it may handle
- Approved information, routine intake, and routing that can be tested against representative cases.
- What needs a person
- Ambiguous requests, sensitive decisions, unhappy callers, and anything outside the approved task.
- What must be agreed first
- Disclosure, consent where required, escalation, quality review, and who maintains the answers and workflow.
Defined in the proposal
The proposal names the trigger, destination, approved messages, consent and opt-outs, failure owner, vendor costs, and any care after launch. Each form, calendar, email, SMS, CRM, or API connection is checked against actual accounts and vendor terms. Sensitive-data handling requires separate review.
Questions that change the build.
Can you connect the tools we already use?
Possibly. We review the exact accounts, permissions, available integrations or APIs, data, and vendor terms before including a connection in a proposal.
What if a handoff fails?
The design needs an exception path and a person who can intervene. Monitoring, response hours, and ongoing support must be agreed for the project; they are not assumed to be available around the clock.
Can the workflow send texts?
SMS may be an option when the use case, consent and opt-out process, vendor setup, and ongoing charges are appropriate. It is not included in every project.
How are automation projects priced?
Custom work is scoped and quoted case by case. The proposal separates the build, third-party charges, and any ongoing support.
Bring us the current inquiry path.
A short call or written summary is enough to start. The recommendation may be a process change, a tool integration, or a larger build.