Fix Forty Voicemail Greetings in One Confirmed Run
Select users on the Users tab, choose an action, review exactly who changes and why, confirm. Greetings are generated per user from one template; setup links let users record their own.
The Users tab grows an Actions bar
Tick users one by one, or tick the header and choose Select all matching to take every user the current search, department and type filters show. A sticky bar counts the selection and opens the Actions menu. Each action is a short form, then a plan, then a confirm. Nothing happens on the PBX until you confirm.
Apply a voicemail greeting
Type the greeting once. Merge fields fill in first name, last name, extension (spoken as digits) and company per user. Pick a voice from the same catalog the AI Voice Studio and the self-service page use, listen to the rendered example for any selected user, and plan. The plan shows how many greetings will be generated and the estimated usage before you spend anything. On apply, each user gets a generated greeting uploaded to the PBX and set as their default, with their other greetings left in place.
Send voicemail setup links
When users should record their own words, choose Send voicemail setup link. Each selected user with an email on file gets a private page, no login, scoped to their extension, where they type the greeting, pick a voice, preview and save. Links expire after the number of days you choose. The plan tells you who has no email before anything is sent.
Built as a framework
Both actions run through the same plan, confirm, worker and audit pipeline, and so does the newest one: turning on 3CX call-quality monitoring for selected extensions. Expect more actions to appear in the same menu.
Frequently asked questions
What does the plan check before I confirm?
Per user: disabled extensions and AI agents are skipped, voicemail-off extensions are skipped, and for greetings a user whose current greeting already matches the template and voice is skipped so no credit is spent. If the PBX connection is not working every user shows as blocked rather than failing halfway.
Does a bulk greeting replace a user's other greetings?
No. Sikurd reads the user's existing greeting set and writes it back with the new file as the active default, so out-of-office, lunch and custom greetings survive.
How fast does a run go and can it hammer the PBX?
Runs execute on Sikurd's worker, one user at a time per instance with a short spacing between writes, and only one run can be active on an instance at a time. A 200-user run finishes in minutes without flooding the PBX.
What is logged?
The run start, every applied or failed user with a redacted before and after, and the completion, all in the instance audit log with the operator's name. Failed users can be retried on their own; nothing is re-fired blindly.
Select the department, not the extension.
Open the live demo, select a department on the Users tab and plan a greeting run. No signup required.
