Give each customer a scoped login and the AI Voice Studio. They create voicemail messages, queue intros, and receptionist greetings themselves, and your helpdesk never sees the ticket.
The ticket that costs more to route than to do
"Please update our after-hours greeting for the holiday weekend" takes ninety seconds of actual work and, in most MSPs, a day of round trips: the office manager emails, the dispatcher makes a ticket, a tech records or begs a WAV file into existence, uploads it in the right format to the right prompt slot, and closes the loop. Multiply by every queue intro, seasonal message, and receptionist menu across your customer base, and voice content quietly becomes one of your noisiest ticket categories.
Sikurd's answer is to hand the ninety seconds to the person who wanted the change, inside guardrails you define.
The AI Voice Studio: type a script, pick a voice, preview, and push straight to the PBX. Demo data shown.
What the client experience looks like
The customer signs into their own portal and sees exactly one phone system: theirs. In the voice tools they can write a script and generate it with a natural AI voice, or upload their own recording; either way Sikurd converts it to the format 3CX expects and applies it to the voicemail box, queue, or digital receptionist they chose. The greeting they wanted at 4:55 pm on Friday is live at 4:57 pm, and nobody at your shop touched it.
What it looks like from your side
You control which clients get access and which surfaces they see. Their changes land in the audit log like anyone else's, and the rest of the PBX is simply not reachable from their login. The result is the good kind of self-service: the client feels ownership of their own phone experience, and your bench keeps its time for work that needs a technician. Pair it with client holiday requests and the entire seasonal-greetings season runs itself.
Frequently asked questions
What exactly can a client change on their own?
Voice content, and only voice content: voicemail messages, queue intro announcements, digital receptionist greetings, and holiday messages, generated from text with the built-in AI voices or uploaded as audio. They cannot touch routing, extensions, trunks, or anything else on the PBX, and they only ever see their own instance.
Do I or my clients need an ElevenLabs account or API key?
No. The ElevenLabs voices are built into Sikurd and covered by the flat per-instance price. There is nothing to sign up for, no key to paste, and no per-character bill arriving later. Your client types the script, picks a voice, listens, and applies it.
How do I know what a client changed?
Every self-service change is written to the audit log with the acting user, the timestamp, and what was applied where, the same trail your own techs' changes leave. If a greeting is suddenly wrong, the answer to 'who changed this?' is one search away.
Fewer tickets for you. Same-day greetings for them.
Client self-service voice tools are included in the flat price, with ElevenLabs voices built in. Try the AI Voice Studio in the live demo, no signup required.
