Each one is hired for a different part of your day. Start with whichever job is costing you the most.
What came in, what the employee did, and what the business gained. Three different jobs, start to finish.
Sample names, businesses and jobs. No live customer data. The tools an employee connects to depend on your setup.
Opsidian handles the routine work without taking control away from you. Anything unusual comes to you first.
Hours, booking slots, spending limits, approved vendors, and the things it must never say. Every employee works inside the boundaries you write.
Anything unusual is held for your approval instead of acted on. The customer hears that someone will confirm, and nothing gets promised in your name.
Every call, message and action is logged with the conversation attached. You see exactly what each employee did, and what is waiting on you.
Rollout and supervision options. What’s available depends on how your deployment is configured.
Four steps, one workflow. Nothing goes live until you’ve seen it handle your work.
Pilot setup
{{ setupStatus }}
In most setups, yes. Your number stays the same and calls forward to your AI employee: all of them, after hours only, or when the line is busy. We confirm what works with your phone provider before the pilot starts.
It says so, holds the request, and brings it to your team with the conversation and details attached. It doesn’t guess or promise anything on your behalf, and a customer can ask for a person at any time.
Yes. In supervised mode, every action waits for your sign-off. Once live, you decide which actions still need approval, such as purchases over a limit or bookings outside your hours.
No. Opsidian works alongside the tools you already use. Which systems an employee connects to depends on your setup, and we confirm that together before anything goes live.
Yes, and that’s how we recommend starting. A pilot is one employee on one workflow, so you see how it handles your work before adding more.