# MagickVoice User Docs > Step-by-step end-user documentation for MagickVoice — an AI voice and messaging platform for placing calls, building phone menus, sending campaigns, and automating follow-ups. Full text of every documentation page, generated from source. --- # Sign in > Sign in to an existing account or create one from the two tabs on the MagickVoice access page. - **Section:** Access - **Audience:** All users - **Page address:** `/login` ## Common tasks - Sign in with email and password - Create an account with email, password, and an optional phone number - Use Google sign-in when your organisation supports it ## How to use this page ### 1. Sign in with email and password Open your existing MagickVoice workspace. 1. Keep the Sign In tab selected. 2. Enter the email address in Email and the matching account password in Password. 3. Select the lower Sign In button below the fields. The tab button at the top only changes the form; it does not sign you in. 4. If the account has not been verified, MagickVoice opens Verify your email. Complete that guide before trying to work in the product. 5. If a temporary network error appears, wait briefly and select Sign In once more. Do not change the credentials unless the page specifically says they are incorrect. ### 2. Create a new account Register an email-and-password account, then move to email verification. 1. Select the Sign Up tab. 2. Enter your email address in Email. The browser focuses this field and explains the problem if the address is blank or not in email format. 3. Enter a new password in Password, then enter exactly the same value in Confirm Password. Both fields are required. 4. Phone Number is optional. If you add one, choose the correct country first and enter the number in that country format; the field displays the completed international number. 5. Select Create Account. While the request is running, the button changes to Please wait... and the Google option is temporarily disabled. 6. After a successful request, sign in with the same email and password if MagickVoice leaves you on the access page. It then opens Verify your email. 7. If the first request shows a network error, wait and try signing in before submitting the signup form again. An email-already-in-use message means the account was created and you should use the Sign In tab. ## Tips and troubleshooting - If a verification message is delayed, check spam, promotions, and any alternate inbox tied to the invite. - Use the same sign-in method your team used when inviting you; switching methods can create a separate account. - The access page also offers Continue with Google. Use the method your organisation expects, otherwise you can create a separate account for the same person. - The page can return a temporary Firebase network message even when the account action completed. Check the next state before repeating an action. ## Related pages - [Verify email](https://docs.magickvoice.com/docs/verify-email) --- # Verify email > Confirm the link sent to your inbox, then ask MagickVoice to recheck the verified account. - **Section:** Access - **Audience:** New and invited users - **Page address:** `/verify-email` ## Common tasks - Open the verification link in your email - Confirm verification in the app - Resend the email when the original message is unavailable - Sign out and use another account ## How to use this page ### 1. Verify your email Confirm the email address shown on the page and continue into MagickVoice. 1. Open the inbox for the email address printed on the page. 2. Find the latest MagickVoice verification message and select the link inside it. Complete any browser confirmation the link presents. 3. Return to the MagickVoice tab and select I've verified my email. 4. The button changes to Checking... while MagickVoice refreshes your account state. 5. When the check succeeds, new accounts open the Dashboard. The Dashboard includes the first-run Getting Started checklist rather than a separate setup wizard. 6. If the first check displays a temporary network error, wait briefly and select I've verified my email once more. ### 2. Send the verification email again Request a new message when the first one does not arrive or has expired. 1. Check Spam or Junk, Promotions, and any filtered inbox folders first. Verification emails can be filtered out of the main inbox. 2. Return to the Verify your email page and select Resend verification email. 3. Wait for the page to confirm that the request finished before checking the inbox again. 4. Open the newest verification message, select its link, then return and select I've verified my email. ## Tips and troubleshooting - If a verification message is delayed, check spam, promotions, and any alternate inbox tied to the invite. - Use the same sign-in method your team used when inviting you; switching methods can create a separate account. - Use Sign out only when the email address on this page is wrong or you need to use a different account. It ends the current session. - A verification link proves email ownership. Selecting I've verified my email is the separate in-app check that lets MagickVoice continue. - If you cannot find the message in your inbox, search for MagickVoice and check Spam or Junk before using Resend verification email. ## Related pages - [Sign in](https://docs.magickvoice.com/docs/sign-in) --- # Dashboard > Use Dashboard as the workspace home page for credit balance, first-run setup, quick actions, and links into every MagickVoice channel. - **Section:** Overview - **Audience:** Workspace operators and admins - **Page address:** `/app` ## Common tasks - Check the active organisation, workspace, and credit balance - Start a first call or browse call scripts - Complete the Getting Started checklist - Open messaging, contacts, scheduling, and channel setup pages ## How to use this page ### 1. Orient yourself on Dashboard Confirm you are in the right workspace and choose the correct starting point. 1. Open Dashboard from Overview in the left navigation. 2. Read the organisation and workspace controls in the top bar, then check the credit balance beside them. 3. Use the welcome panel for a direct first action: select Make your first call to open the call form, or Browse call scripts to choose or create an AI call script. 4. Leave the Page guide expanded the first time you use Dashboard. It explains how credit balance, activity, and channel cards relate to the rest of MagickVoice. 5. Use the profile control in the top-right corner only for account-level actions. It is separate from the workspace selector and channel navigation. ### 2. Complete the Getting Started checklist Set up the minimum pieces needed to run a useful first voice workflow. 1. Find Getting Started below the Page guide. The progress label shows how many of the four tasks have been completed. 2. Select Go next to Create a call script to define what the AI should do during a call. 3. Return to Dashboard, then select Go next to Upload a contact list to import the people your campaigns or calls will reach. 4. Select Go next to Make your first call when you are ready to test the script with a real recipient. 5. Use Schedule a campaign when the first call works and you want to plan a group of calls for a future time. 6. Do not dismiss the checklist while you still need its links. Dismiss hides the guide; it does not finish or undo any setup task. ### 3. Use a quick action or channel card Jump directly into the type of work you want to do without navigating through multiple menus. 1. Use Send Message to open the messaging workflow, Upload Contacts to open contact-list import, or Schedule Campaign to plan a future campaign. 2. Use the AI calls card to start voice-call setup, Phone menus to build a press-a-key menu, Voice messages to prepare an announcement, or Messaging to connect a supported message channel. 3. After choosing a card, use the destination page for detailed configuration. Dashboard is a launch point, not the place where you enter all campaign or call settings. ## Tips and troubleshooting - Treat dashboard numbers as a starting point, then open the linked page for row-level detail. - Use the dashboard after major campaigns to spot failed calls, low balance, or pending setup work quickly. - The credit balance updates as calls start and finish. Open the Credits page from the balance when you need to review or add credits. - Channel cards are shortcuts to detailed records and setup pages. Use them to narrow the task, then continue in the linked feature area. - If the welcome panel or checklist is hidden, Dashboard still remains the same home page; use the left navigation to reach Calls, Call scripts, Contacts, Scheduling, and Messaging directly. --- # Calls > Monitor AI call activity, narrow the list to the records that matter, export it when needed, and start one-off calls. - **Section:** Voice - **Audience:** Voice operators - **Page address:** `/app/calls` ## Common tasks - Filter AI call records - Search for one exact phone number - Export the visible data - Start a single AI call ## How to use this page ### 1. Find the calls you need Reduce a long call list to a precise operational view. 1. Open Voice, then Calls. The table shows each AI call with its status, direction, pipeline, provider, duration, talk time, recording indicator, and time. 2. Use All Statuses to isolate outcomes such as Queued, Ringing, In Progress, Completed, Failed, No Answer, Busy, or Switched Off. 3. Use pipeline, provider, and direction filters when you need to compare the same type of call. The phone search is an exact match, so enter the complete number with its country code. 4. Use Filter by Batch ID when investigating a known batch. Use the Duration or Talk Time column headings to sort the resulting table. 5. Check the outcome text and recording indicator before continuing with any follow-up. Select the conversation follow-up control only when you are ready to continue work on that contact. ### 2. Export or choose the right calling workflow Use this page without accidentally starting a bulk job from the legacy area. 1. Apply the filters first; Export CSV exports the data currently represented by your filtered view. 2. Use Customize export columns to decide which call fields are included before exporting. 3. Select New Call for one AI-assisted outbound call. Complete its required recipient, caller ID, prompt, and AI quality fields before the call button becomes available. 4. For a list of recipients, use Open the Campaign Composer in the notice. The page explicitly marks Bulk Calls here as a retiring workflow. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - A completed status means the call finished; it does not by itself indicate the business outcome. Review the call context before marking the work done. - Do not use the exact-number search with a partial local number. Include the plus sign and country code to avoid an empty result. ## Related pages - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) - [Call detail](https://docs.magickvoice.com/docs/call-detail) --- # New call > Configure and launch one outbound AI call with the recipient, caller ID, script, quality, recording, and scheduling controls in one guided form. - **Section:** Voice - **Audience:** Voice operators - **Page address:** `/app/calls/new` ## Common tasks - Enter the recipient - Choose the displayed caller ID - Select the script and AI quality - Schedule or start one call ## How to use this page ### 1. Set up a single AI call Provide the information the AI needs to call the right person from the right number. 1. In Who are we calling?, enter Phone number with the country code, for example +91 for India. This field is required. 2. Optionally enter Their name. It helps the AI greet the recipient more personally. 3. Choose Call from. This is the MagickVoice number the recipient sees when the phone rings. If the selector is still loading, wait for the workspace phone numbers to load rather than entering a number manually. 4. Under What should the AI say?, choose a Prompt template. A template is the reusable script that directs the AI during the conversation. 5. Choose the AI quality that matches the conversation. Higher tiers are described on screen as more natural and better at handling conversation. Then choose a Voice after selecting a quality tier. ### 2. Choose call behavior and launch time Make the one-off call with the intended safeguards. 1. Select a Language only when the prompt is configured to use it. Selecting a language makes it available, but the prompt instructions must explicitly tell the agent to speak that language. 2. Leave Record this call on when you need an audio copy for review. The screen notes that recording has a small additional charge. 3. Turn on Detect answering machines when voicemail detection is useful. Use Attach automations or Advanced settings only when your workflow requires them; advanced settings are for reference ID and developer options. 4. Choose Send Now to place the call after review, or Schedule for Later to choose a future date and time. 5. Read the helper line above the action buttons. It lists every missing requirement. Start call now becomes available only after valid phone number, caller ID, prompt template, and AI pipeline are set. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - Use this page for one recipient. For a group of recipients, select Try the Campaign Composer instead of repeating individual calls. - Cancel leaves the setup screen without placing a call. Starting a call is an external action, so review the caller ID, recipient, and script together before selecting it. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) - [Call detail](https://docs.magickvoice.com/docs/call-detail) --- # Dialer > Call a phone number directly from the browser by selecting an approved caller ID, entering a full phone number, and acknowledging recording consent when needed. - **Section:** Voice - **Audience:** WebRTC dialer users - **Page address:** `/app/calls/dialer` - **Access:** Your admin may need to enable this feature ## Common tasks - Select a caller ID - Enter or key in a full number - Choose whether to record - Place a browser call ## How to use this page ### 1. Place a browser-dialer call Call a number from the browser with the correct visible caller ID. 1. Open Voice, then Dialer. Use Call history in the page header when you need previous browser-dialer records instead. 2. Choose Caller ID. This is the active workspace number the recipient will see; only available tenant numbers appear in the selector. 3. Enter Number to call with the country code. You can type it directly or use the keypad. Hold 0 on the keypad to enter a plus sign. 4. Select Record this call only if recording is appropriate. The page explicitly reminds you to make sure everyone on the call consents to being recorded. 5. Review the caller ID and recipient number, then select Call. The call button remains unavailable until the required information is present. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - The Credits panel shows the available workspace balance and the approximate per-minute talk-time rate. Confirm there is enough balance before a longer call. - Use a complete international number. The dialer accepts the number you intend to reach, not a contact name. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) - [Call detail](https://docs.magickvoice.com/docs/call-detail) --- # Dialer call history > Review calls that were placed from the browser dialer, filter them by final status or exact number, view AI-generated summaries and transcripts, and open the dialer to make the next call. - **Section:** Voice - **Audience:** WebRTC dialer users - **Page address:** `/app/calls/dialer/history` - **Access:** Your admin may need to enable this feature ## Common tasks - Filter browser calls by status - Search an exact number - View call summaries and transcripts - Refresh the call log - Open the dialer ## How to use this page ### 1. Find a browser-dialer record Confirm the result of a call placed from your browser. 1. Open Voice, then Call History. This history is specifically for calls placed from the browser dialer, not the wider AI Calls list. 2. Use All Statuses to limit the view to Initiating, Ringing, In Progress, Completed, Failed, No Answer, Busy, or Canceled calls. 3. Use Search phone (exact) with the full country-code number when you know the recipient. 4. Select Refresh after a recent call finishes if its record has not appeared yet. 5. If there are no records, use Open Dialer to make the first browser call. The empty-state message changes after a call is logged. ### 2. View call summaries and transcripts Review what was discussed on completed dialer calls, just like AI calls. 1. Select a completed call from the history list to open its detail page. 2. Scroll to the Call Analysis section to read the AI-generated summary of the conversation, key topics discussed, and overall sentiment. 3. Continue to the Transcript section to see the full turn-by-turn conversation with timestamps and speaker labels, similar to how AI call transcripts are presented. 4. Use the summary to quickly understand what happened on the call without listening to the full recording, saving time when reviewing many calls. 5. Summaries and transcripts are generated after the call completes. They appear automatically on the [call detail](/docs/call-detail) page for dialer calls, alongside the recording and delivery facts. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - An AI call initiated from Calls is not the same as a browser-dialer call. Check the correct history before assuming a record is missing. - A call that is still initiating or ringing may take time to reach a final outcome. Refresh instead of placing a duplicate call. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Call detail](https://docs.magickvoice.com/docs/call-detail) --- # Call detail > Open a completed AI call or dialer call from Calls to review its delivery facts, recording, AI-generated outcome analysis, and turn-by-turn transcript before deciding on a follow-up. - **Section:** Voice - **Audience:** Voice operators and managers - **Page address:** `/app/calls/:id` ## Common tasks - Review delivery facts - Play or download a permitted recording - Interpret call analysis - Read the transcript - Choose a follow-up ## How to use this page ### 1. Open the right call and confirm the delivery facts Establish what happened before relying on interpretation or taking another action. 1. In Voice, open Calls. Narrow the list by status, direction, provider, pipeline, exact phone number, or batch ID until the correct record is visible. 2. Select the call row to open Call Detail. Start at Call Information rather than jumping straight to the transcript. 3. Check Phone and Recipient to confirm that this is the correct person. These values are customer data, so do not copy them into an unapproved channel. 4. Read Status and its plain-language outcome first. Then use Direction, Pipeline, Provider, and Language to understand how the call was routed and configured. 5. Compare Created, Answered, and Ended with Duration and Talk Time. Duration covers the complete call lifecycle; talk time reflects the connected conversation portion. 6. Use See credits when you need to investigate the cost associated with the call. If Template Variables appear below the facts, they show the values that were inserted into the script for this recipient. ### 2. Review a recording responsibly Verify the actual audio without exposing call content unnecessarily. 1. Scroll to Recording. When a recording exists, use Play, the elapsed-time display, waveform, and volume control to review the audio in place. 2. Use the player to check material questions such as whether the call connected clearly, whether a hand-off was understood, or whether the transcript reflects what was said. 3. Use Download only when you are authorized to retain a local copy. The recording can contain personal and commercially sensitive information. 4. If no recording is shown, check whether recording was enabled for the call and whether your role is allowed to view it before assuming the call failed. ### 3. Understand the generated call analysis Use the analysis as a fast review aid while keeping human judgement in the decision loop. 1. Scroll to Call Analysis. Read the generated summary first to understand the stated request, response, and apparent outcome without replaying the entire call. 2. Use Overall Sentiment and its score as a directional signal for the conversation tone. A score is not a customer commitment and should not be used by itself to trigger a high-impact action. 3. Review Key Topics to see the issues or requests detected in the call. Use them to route the record to the right team or to check whether a required subject was covered. 4. Use Conversation Quality to compare Coherence and Effectiveness Score on their 10-point scales. Resolution Achieved indicates whether the analysis judged the stated objective to be met. 5. Open the recording or transcript when a score, topic, or summary does not match the operational outcome you expect. ### 4. Read the transcript and take a follow-up action Confirm the details that matter and continue the customer relationship in context. 1. Continue to Transcript. Each entry is labelled Assistant or User, includes a timestamp, and shows the sentiment detected for that turn. 2. Read in sequence to distinguish an explicit agreement from a question, a proposed alternative, or an unresolved objection. Use the recording when exact wording or tone matters. 3. Compare the final transcript turn with Resolution Achieved before marking work complete or starting another contact attempt. 4. Use Follow up at the top of the page only after reviewing the record. Choose the available conversation action that matches the confirmed outcome rather than creating a duplicate interaction. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - Analysis, sentiment, and transcripts are generated aids. Check the recording or the operational facts before making a consequential customer, billing, or compliance decision. - A completed call can still have a short talk time. Compare the timestamps, duration, recording, and transcript before deciding that the objective was achieved. - Treat recordings, transcripts, template values, and contact information as customer data. Follow your organization’s retention, export, and access rules. - If a call failed or did not answer, use the delivery facts to check the number, caller ID, provider, and final outcome before retrying. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) --- # Conversation thread > Use the contextual conversation timeline to understand the most recent customer interaction before continuing a call or message follow-up. - **Section:** Voice - **Audience:** Support and follow-up users - **Page address:** `/app/threads/:id` ## Common tasks - Review the latest interaction - Find related call context - Choose the next follow-up - Return to the originating Voice record ## How to use this page ### 1. Continue a conversation in context Avoid losing the history behind a follow-up. 1. Start from the relevant call record or its Follow up on this conversation control. 2. Read the newest timeline entry before composing or starting another interaction. 3. Open related call or message context when you need the reason for a prior status or outcome. 4. Carry out the next customer action only after confirming it belongs to the same contact and conversation. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - A conversation thread is context, not a signal to contact someone again automatically. Check the latest outcome first. - Return to the original call record when you need its technical result, duration, recording indicator, or provider information. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) --- # Call scripts > Create, reuse, export, edit, and remove the AI call scripts that tell a voice agent what to say and do on the phone. - **Section:** Voice - **Audience:** Script authors - **Page address:** `/app/prompts` ## Common tasks - Create a call script - Import a script from JSON - Edit an existing script - Export or delete a script ## How to use this page ### 1. Manage a reusable call script Keep voice-agent behavior organized and ready for safe use in calls and campaigns. 1. Open Voice, then Call Scripts. The count beside the heading shows how many scripts exist; each card lists the script name, its enabled language chips, and its guideline count. 2. Select Create call script to build a new script from a template or a blank canvas. Select Edit on an existing card to open the same editor for that script. 3. Use Import JSON only with a script file you have reviewed. Use Export as JSON on a card to save a script definition for transfer or backup. 4. Use Delete on a card only when the script is no longer needed. Confirm it is not selected by a live call or campaign before removing it. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - The page guide points to the Quick Start templates for common use cases and reminds you to test a script from the editor’s Test tab before using it with real customers. - Language chips reflect which languages the script enables; the instructions still have to tell the agent which language to actually speak. - Export a script before a major rewrite when you want an easy rollback reference. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) --- # Call transfers > Set up human transfer destinations so an AI agent can hand off a live call to a person when help is needed. Define transfer destinations in a call script, test them before going live, and let the AI decide when escalation is appropriate based on the conversation. - **Section:** Voice - **Audience:** Script authors and voice operators - **Page address:** `/app/prompts/:id/transfer-destinations` ## Common tasks - Configure transfer destinations in a call script - Test a transfer destination - Review transfer outcomes - Update or remove transfer destinations ## How to use this page ### 1. Understand what call transfers are Know when and why to use human escalation before you configure it. 1. A call transfer hands off a live AI call to a real person when the AI determines someone needs human assistance. The AI stays on the line until the transfer completes, then disconnects. 2. Transfer destinations are configured per call script. Each destination is a phone number and a label (for example "Sales team" or "Support hotline"). 3. The AI decides when to transfer based on the conversation context and the instructions in your call script. Write clear transfer guidelines in the script's instructions so the AI knows when escalation is appropriate. 4. Use transfers when customers need help the AI cannot provide — complex issues, sensitive matters, or explicit requests to speak with a person. ### 2. Configure transfer destinations in a call script Set up the phone numbers the AI can transfer to, so escalation works when needed. 1. Open Voice, then Call Scripts. Select a script or create a new one. 2. In the script editor, find the Transfer Destinations section. This is where you define the roster of people or teams the AI can transfer to. 3. Select Add destination. Enter a descriptive Label (for example "Billing support" or "Sales team") and the Phone number to transfer to, including the country code. 4. Add as many destinations as your workflow needs. Each one appears in the roster with its label and number. 5. Use Edit on a destination to change its details, or Remove to delete one you no longer need. 6. Save the call script after adding or changing destinations. ### 3. Test a transfer destination Confirm a destination works before using it in live calls, so customers are not left waiting when they need help. 1. In the Transfer Destinations section of the script editor, find the destination you want to test. 2. Use the Test action on that destination. The platform places a live test call to the configured number. 3. Answer the test call when it arrives to confirm the number is correct and reachable. A working test proves the destination is ready for live transfers. 4. Repeat the test whenever you change a destination's phone number or add a new one. 5. Remove or fix any destinations that fail the test before launching a campaign with this script. ### 4. Write clear transfer instructions in your call script Tell the AI when and how to transfer, so it escalates appropriately. 1. In your call script's instructions, describe the situations when the AI should transfer — for example "If the customer asks to speak with a person, transfer to Sales team" or "If the issue is about billing and the customer is frustrated, transfer to Billing support." 2. Be explicit about which destination to use for which situation, especially when you have multiple transfer options. 3. Include any required preamble or handoff message the AI should say before initiating the transfer, such as "Let me connect you to someone who can help." 4. Test the full conversation flow with a sample call to confirm the AI transfers at the right moment with the right destination. ### 5. Review transfer outcomes Track how often calls are escalated and whether transfers succeed. 1. After a call is transferred, open the [call detail](/docs/call-detail) page for that call to see the transfer outcome in the call information panel. 2. Check the transcript to understand what triggered the transfer and whether the AI followed your instructions correctly. 3. If transfers are happening too often or not often enough, adjust the instructions in your call script and test again. 4. Use the status and outcome filters on [Calls](/docs/calls) to find transferred calls and review their patterns over time. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - Test each transfer destination before using it in a live campaign to confirm the number works and a human answers. - The AI decides when to transfer based on the conversation flow and its instructions — make those instructions clear in the call script. - A transferred call leaves the AI and becomes a regular person-to-person phone call, so standard per-minute charges apply for the remaining duration. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) --- # Create or edit a call script > Build a new AI call script from a template or blank canvas, or edit an existing one, using the same structured editor of sections for instructions, guardrails, silence handling, languages, integrations, and captured outcomes. - **Section:** Voice - **Audience:** Script authors - **Page address:** `/app/prompts/new` ## Common tasks - Start from a template or blank canvas - Write agent instructions and the opening message - Set rules, hand-off, silence, and languages - Preview, test, and save ## How to use this page ### 1. Choose a starting point Begin with structure that matches the call type, whether the script is new or an edit. 1. For a new script, select Create call script from Call Scripts, then either pick an industry category and template or select Start from scratch (blank canvas). 2. To change an existing script, select Edit on its card. The editor opens titled with the script name and shows a Save changes button instead of Save script; new scripts show New call script and a Save script button. 3. Work through the left-hand sections in order. Name and What your agent should do carry a needs-attention marker until they are complete, and the save button stays disabled until the required information is present. ### 2. Define how the agent speaks and behaves Give the agent specific, usable instructions rather than a vague topic. 1. In Name, give the script a name you can find later. This field is required. 2. In What your agent should do, write Instructions for your agent — the role, objective, boundaries, and desired outcome. Use Improve writing for a refinement suggestion, and Personalize to insert per-recipient details such as a name into the text. 3. Add the Opening message: the first line the agent speaks when the call connects. Personalized fields you insert appear as chips in both the instructions and the opening message. 4. In Do’s and don’ts, add concrete rules the agent must follow, and under When to hand off to a person, list the situations that should pass the call to a human. ### 3. Tune silence, languages, and captured data Set the operational behavior that keeps calls on track. 1. In If the caller goes quiet, enable Silence handling to reveal the Directive (what the agent says when the caller is quiet), Threshold in seconds before nudging, and Max nudges before ending the call. Note that the highest voice-quality tier does not support nudging, so these settings have no effect there. 2. In Languages it can speak, check the languages to make them selectable at call time. Checking a language only makes it available — the agent speaks another language only if your instructions explicitly tell it to (for example, “Speak in Tamil”). 3. Use What to capture from each call to add specific details to note from every conversation, such as whether the caller agreed to pay. 4. Use Connect to your systems when the agent must look up information mid-call. This section, along with Preview and Test, requires you to save the script first, so save once the required sections are complete and continue editing. ### 4. Preview, test, and save Confirm the script behaves as intended before using it live. 1. Use the Preview tab to inspect the rendered opening message and instructions. For a saved script, fill the personalized sample fields so the preview shows realistic values. 2. Switch to the Test tab to exercise the script on a real test call. Both Preview detail and Test require the script to be saved first. 3. Select Save script (new) or Save changes (edit) once the preview matches the intended behavior. For a significant edit, run the revised script on a single call before broad use. 4. Use Close to leave the editor. Closing before saving discards the unsaved draft, so save a working version before a large experimental change. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - New and edit use the same editor and the same sections; an edit changes the reusable script, so assume it affects future calls and campaigns that select it. - Keep instructions concrete: say what the agent should do, what it must not do, and when it must hand off. That is more reliable than a short topic-only prompt. - If you need to preserve the original behavior, export the script before a major rewrite or create a separate script for the new use case. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) --- # SIP Connections > Connect an approved SIP trunk so MagickVoice can place outbound calls through your carrier, using either SIP credentials or an IP allowlist. - **Section:** Voice - **Audience:** Telephony administrators - **Page address:** `/app/sip/connections` ## Common tasks - Add a SIP connection - Enter the trunk domain - Choose credentials or IP allowlist - Allow MagickVoice egress IPs ## How to use this page ### 1. Add a credential-based SIP trunk Save the connection details supplied by a carrier that authenticates with a SIP username and password. 1. Open Voice, then SIP Connections, and select Add SIP Connection. 2. Enter a clear Connection Name, such as the carrier name and intended environment, so users can recognize it later. 3. Enter the SIP Domain exactly as provided by the carrier. Include a port only when one is required, but do not include the sip: prefix. 4. Leave Credentials selected, then enter the SIP username and SIP password from the carrier. The form notes that credentials are encrypted at rest. 5. Review the values and create the connection. Use it first with a controlled test call before routing operational calling through it. ### 2. Use IP allowlisting instead Connect a trunk that trusts MagickVoice network addresses rather than a SIP username and password. 1. Enter the connection name and SIP domain as above, then select IP whitelist as the authentication mode. 2. Create the connection without entering credentials. 3. Open the saved connection’s detail page and find the Egress IPs to Whitelist section. If the addresses are listed, copy them; if the section says they are not available yet, contact support to obtain them. 4. Allow those addresses on the SIP trunk or firewall with your carrier. Calls cannot authenticate until the carrier-side allowlist is in place. ### 3. Review or remove an existing connection Manage the trunks already saved in the workspace. 1. Once connections exist, the page lists them in a table with Name, SIP Domain, Auth Mode, Calls Placed, Test result, Status, and Created date. 2. Select a row to open its detail page, or use the row’s Edit control to change its settings. 3. Use Revoke to take a trunk out of service. A confirmation warns that calls relying on it will fail, so confirm only when nothing live depends on that route. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - A SIP connection can direct outbound call traffic through your carrier. Coordinate ownership and testing with the person who manages the carrier account before saving production settings. - If the carrier gives a hostname with a non-standard port, include the port after the hostname, for example sip.example.com:5060. - Use a distinct connection name for sandbox and production trunks so the correct route is obvious during call setup. - SIP trunks are used only when the effective telephony provider supports them (VoBiz). If your workspace is on another provider, a saved connection will not carry calls until that provider is in effect. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) --- # SIP connection detail > Inspect one SIP connection: its domain and authentication mode, status and usage, the egress IPs to allowlist for IP-whitelist trunks, and the controls to test, edit, or revoke it. - **Section:** Voice - **Audience:** Telephony admins - **Page address:** `/app/sip/connections/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Review connection information and status - Copy the egress IPs to allowlist - Test the connection - Edit or revoke the connection ## How to use this page ### 1. Review and verify a SIP connection Confirm a trunk is configured correctly and ready to carry calls. 1. Open Voice, then SIP Connections, and select the connection row. The detail page opens with a breadcrumb back to the list and the connection name and status in the header. 2. Check Connection Information for the SIP Domain, Auth Mode, Status, VoBiz Trunk ID, and the Created, Updated, Last Used, Last Tested, and Last Test Error values. The cards below summarize Calls Placed and the Last Test result. 3. For an IP-whitelist trunk, use Egress IPs to Whitelist to get the addresses to allow on your carrier’s SIP trunk or firewall. If it reads that IPs are not available yet, contact support to obtain them, as the note on the page instructs. 4. Select Test Connection to run a connectivity check; the Last Tested and Last Test Error fields record the outcome. Run a test before routing production calls through the trunk. ### 2. Edit or revoke a connection Change trunk details or take a trunk out of service safely. 1. Select Edit to change the connection name, SIP domain, authentication mode, or credentials, then save. 2. Select Revoke to take the trunk out of service. A confirmation dialog warns that calls relying on this trunk will fail, so confirm only when no live calling depends on it. 3. Coordinate edits and revocation with the person who manages the carrier account, since both can interrupt outbound calling. ## Tips and troubleshooting - Open the detail page after a call to review transcript, outcome, recording, and follow-up options in one place. - When comparing calls, use status and date filters first, then open only the calls that need action. - Egress IPs are shown here rather than on the list page. For an IP-whitelist trunk, calls cannot authenticate until those addresses are allowed on the carrier side. - Last Used and Last Tested help confirm whether a trunk is actually carrying traffic before you revoke or reconfigure it. - Revoking a connection is disruptive, not a soft toggle — the confirmation states that dependent calls will fail, so treat it as taking the route offline. ## Related pages - [Calls](https://docs.magickvoice.com/docs/calls) - [New call](https://docs.magickvoice.com/docs/new-call) - [Dialer](https://docs.magickvoice.com/docs/dialer) - [Dialer call history](https://docs.magickvoice.com/docs/dialer-call-history) --- # Phone menus > Manage IVR workflows — automated call flows that greet callers, offer press-a-key menus, collect input, route the call, or hand it off to an AI assistant — and open the visual builder to create or change one. - **Section:** Phone Menus - **Audience:** IVR builders - **Page address:** `/app/ivr-workflows` - **Access:** Your admin may need to enable this feature ## Common tasks - Create a workflow from a template - Import a workflow - Edit an existing workflow - Export or delete a workflow ## How to use this page ### 1. Manage your phone menu workflows Keep IVR call flows organized and ready to attach to live calling. 1. Open Phone Menus. The count beside the heading shows how many workflows exist; the table lists each workflow with its description, step count, variable count, version, status (for example Active), and when it was last updated. 2. Select Create workflow to start from a ready-made template or a blank canvas. Select Edit on a row to open the same builder for that workflow. 3. Use Import only with a workflow file you have reviewed, and Export on a row to save a workflow definition for transfer or backup. 4. Use Delete on a row only when the workflow is no longer needed. Confirm it is not attached to a live number or campaign before removing it. ## Tips and troubleshooting - Use short labels for IVR steps so the canvas remains readable as the menu grows. - Test no-input and invalid-input paths; they are the most common places callers get stuck. - The page guide explains that each workflow is a sequence of steps — play audio, gather input, make a decision, call a webhook, or hand off to an AI assistant. - Test a workflow before going live by launching a small batch from the Campaign Composer, then review the run on Menu Activity. ## Related pages - [Create or edit a phone menu](https://docs.magickvoice.com/docs/create-or-edit-a-phone-menu) - [Menu activity](https://docs.magickvoice.com/docs/menu-activity) - [Menu session detail](https://docs.magickvoice.com/docs/menu-session-detail) --- # Create or edit a phone menu > Build a new IVR workflow from a template or a blank canvas, or edit an existing one, in the same visual builder: a step palette on the left, the call-flow canvas in the middle, the selected step’s settings on the right, and a dock for problems, variables, and a no-cost simulator. - **Section:** Phone Menus - **Audience:** IVR builders - **Page address:** `/app/ivr-workflows/new` - **Access:** Your admin may need to enable this feature ## Common tasks - Start from a template or blank canvas - Add and connect call steps - Configure each step’s settings and routes - Simulate, resolve problems, and save ## How to use this page ### 1. Choose a starting point Begin with a structure that matches the call flow, whether the workflow is new or an edit. 1. For a new workflow, select Create workflow from Phone Menus, then pick a template — Blank workflow, Greeting → talk to AI, Press-1 phone menu, Verify a code, or Satisfaction survey. Each template card shows how many steps it starts with. 2. To change an existing workflow, select Edit on its row. The builder opens on the same canvas; a header shows the workflow name, the step count, and whether the flow is ready to save. 3. Give the workflow a clear name in the name field at the top so it is easy to find later. ### 2. Build the caller’s journey Lay out the steps a caller moves through, from greeting to a final destination. 1. From the Add to the call palette, add steps: Play message (speak text-to-speech or an uploaded clip), Gather input (ask the caller to press keys and save the result to a variable), Decision (branch on a collected value), Webhook (call an external service mid-call), AI handoff (connect the live caller to an AI assistant — a terminal step), and Hang up (end the call, optionally with a final message). 2. Select any step on the canvas to edit it in the right-hand inspector. For a Play message step you set the Title, the required Step ID (used to wire routes), what the caller hears, and the Language and Voice; High-quality audio pre-generates natural-sounding speech instead of the phone network’s robotic text-to-speech. 3. Routes read in caller language on the canvas — “if the caller presses 1”, “no input”, “otherwise” — so the branches show exactly how a caller reaches each step. 4. Use Undo and Redo while you arrange steps. Only blocking problems stop you saving; reachability and variable hints are advisory. ### 3. Step type — Play message (Speak) Speak something to the caller — a greeting or read-out information — then continue down the call line. Plays text-to-speech or an uploaded audio clip. 1. What the caller hears: the text spoken via text-to-speech. Use {{variable}} to insert values collected earlier in the call. 2. Language and Voice: the language and voice used to speak the message; leave on Default to inherit the workflow’s settings. 3. High-quality audio: pre-generates natural-sounding speech through the provider instead of the phone network’s robotic text-to-speech, and falls back to standard audio if it cannot be generated. 4. Audio file: choose an uploaded clip to play instead of the text — upload clips under Audio Files first. Advanced options add a Loop count to repeat the message before continuing (defaults to once). 5. Use it to open the call, read back information, or bridge between steps. ### 4. Step type — Gather input (Listen) Ask the caller to press keys and save what they enter into a variable you can branch on later — a menu choice, an OTP, or any keypad input. 1. What the caller hears: the prompt played before input, for example “Press 1 for sales, or 2 for support.” Supports {{variable}} personalization. 2. Save the answer as: the required variable name the keypad input is stored under (for example menu_choice) so later steps can test it or pass it to the AI. 3. Digits: how many keypad digits to collect (1–20). Timeout: seconds to wait for input before treating it as no input (1–120). Retries: how many times to re-prompt after no input (0–10). 4. If the caller gives no input: where to send the caller after they run out of retries; leave blank to continue down the call line. 5. Language, Voice, and High-quality audio behave as they do for Play message. Use it whenever the flow needs a decision or data from the caller. ### 5. Step type — Decision (Decide) Route the caller differently based on a collected value — “if they pressed 1, do this; otherwise, do that.” Adds no audio; it only chooses a path. 1. Decide based on: the collected variable to test (for example menu_choice). Every rule below compares this value. 2. Rules: each rule is an operator — Equals, Not equals, In (list), Greater than, or Less than — a value, and a destination step. Each rule peels off the canvas as a labeled detour, and the first matching rule wins. 3. Otherwise (no rule matched): the catch-all destination when no rule matches; leave blank to continue down the call line to the next step. 4. Use Add rule to add more branches. Use it right after a Gather input step to send each keypad choice to the right place. ### 6. Step type — Webhook (Decide) Call an external service mid-call to fetch or send data — for example look up an account — and optionally save the response and reroute on failure. 1. Endpoint URL (required) and Method (POST or GET): the service to call; use {{variable}} in the URL to pass collected values. 2. If the request fails: where to send the caller if the service errors or times out. 3. Advanced — Save response as: store the response (or a field of it) under a name for later steps. Request body: a JSON template sent with the request, using {{variable}} placeholders. 4. Advanced — Timeout (500–30000 ms) and Retries (0–5) control how long to wait and how many times to retry. Wait message plays to the caller while the request runs. 5. Use it to personalize the flow with live data, such as branching on an account status returned by your system. ### 7. Step type — AI handoff (Connect) End the IVR and connect the live caller to an AI assistant on the same line. A terminal step — nothing runs after it — and variables collected earlier flow into the AI prompt automatically. 1. AI prompt template (required): the call script the AI agent uses once it takes over; choose one of your saved Call Scripts. 2. AI’s opening line: the first thing the AI says when it takes over, with {{variable}} personalization. 3. Prompt variables: map collected values into the prompt — the builder offers quick chips such as {{menu_choice}} for the values already gathered. 4. Advanced — AI quality sets an optional quality tier (Bronze through Platinum, or the server default) and Language sets the language the AI converses in. 5. Use it to let callers self-serve through the menu and then talk to the AI for anything the menu cannot handle. ### 8. Step type — Hang up (End) End the call cleanly, optionally after a final message. A terminal step — the call ends here. 1. Final message: an optional line played to the caller right before the call ends, for example “Thanks for calling. Goodbye!” 2. Language and Voice control how that final message is spoken. 3. Use it to close every branch of the flow so callers always reach a defined ending rather than dropping off unexpectedly. ### 9. Simulate, resolve problems, and save Confirm the flow routes correctly before it handles live callers. 1. Open the Problems tab in the dock. Items there are clickable and jump straight to the step that needs attention — for example “Webhook step needs a valid URL”, “prompt_template_id is required”, or a step that “can’t be reached from the start of the flow”. The flow is ready to save when it reports no blocking problems. 2. Use the Variables tab to review the values the flow collects and references, such as menu_choice. 3. Open the Simulator, set the sample call details (for example a phone value and a menu_choice), and select Run call to walk the flow step by step. Nothing is dialed and no credits are spent. 4. Select Save once the flow is correct. For a significant edit to a live workflow, simulate the revised routing first, since an edit changes the flow that future calls will follow. ## Tips and troubleshooting - Use short labels for IVR steps so the canvas remains readable as the menu grows. - Test no-input and invalid-input paths; they are the most common places callers get stuck. - New and edit use the same builder and the same steps; an edit changes the workflow that live calls follow, so treat it as affecting callers already routed through it. - Give every step a clear Title and a stable Step ID — routes wire to the Step ID, so renaming or removing a step can break the branches that point to it. - Test the no-input and invalid-input paths in the Simulator; they are the most common places callers get stuck. ## Related pages - [Phone menus](https://docs.magickvoice.com/docs/phone-menus) - [Menu activity](https://docs.magickvoice.com/docs/menu-activity) - [Menu session detail](https://docs.magickvoice.com/docs/menu-session-detail) --- # Menu activity > Review IVR call sessions — one session per phone call through a workflow — and filter them by status, workflow, phone number, or batch to see how callers moved through your menus. - **Section:** Phone Menus - **Audience:** IVR operators - **Page address:** `/app/ivr-sessions` - **Access:** Your admin may need to enable this feature ## Common tasks - Filter sessions by status or workflow - Search for one exact phone number - Filter by batch ID - Open a session to inspect the caller path ## How to use this page ### 1. Find and review IVR sessions Locate the right call sessions and understand how callers moved through a menu. 1. Open Menu Activity. Use the status filter (Queued, Ringing, In Progress, Completed, Failed, No Answer, and more), the workflow filter, Search phone (exact) with the full country-code number, or Batch ID to narrow the list. 2. Active sessions auto-refresh about every 10 seconds, so you can watch progress live; use Refresh to update immediately. 3. Open a session to inspect the caller path — the steps taken, keypad input, and where the call ended — when you need to investigate an abandoned or misrouted call. 4. To launch new IVR calls, use Open the Campaign Composer. Batch initiation has moved there and running batches from this page is being retired. ## Tips and troubleshooting - Use short labels for IVR steps so the canvas remains readable as the menu grows. - Test no-input and invalid-input paths; they are the most common places callers get stuck. - The phone search is an exact match — enter the complete number with its country code, for example +919876543210. - Session data reflects real caller activity and may include customer phone numbers; treat it as customer data and do not copy it into unapproved channels. ## Related pages - [Phone menus](https://docs.magickvoice.com/docs/phone-menus) - [Create or edit a phone menu](https://docs.magickvoice.com/docs/create-or-edit-a-phone-menu) - [Menu session detail](https://docs.magickvoice.com/docs/menu-session-detail) --- # Menu session detail > Inspect a single IVR session, including route choices, timing, and the caller journey. - **Section:** Phone Menus - **Audience:** IVR operators - **Page address:** `/app/ivr-sessions/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Review caller path - Inspect keypad input - Identify routing problems ## How to use this page ### 1. Use this page to build or review IVR phone menus Understand what is available on Menu session detail and choose the right next action. 1. Open Menu session detail from the Phone Menus area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use short labels for IVR steps so the canvas remains readable as the menu grows. - Test no-input and invalid-input paths; they are the most common places callers get stuck. ## Related pages - [Phone menus](https://docs.magickvoice.com/docs/phone-menus) - [Create or edit a phone menu](https://docs.magickvoice.com/docs/create-or-edit-a-phone-menu) - [Menu activity](https://docs.magickvoice.com/docs/menu-activity) --- # Automations > Manage post-call follow-up automations — chained actions that send a Telegram, WhatsApp, or email message, or call a webhook, after a call completes, conditional on the call outcome, IVR responses, or analysis results. The same automation can be reused across single calls, bulk dispatches, and schedules. - **Section:** Automations - **Audience:** Operations users - **Page address:** `/app/automations` ## Common tasks - Create a new automation - Review the automations table - Open an automation's detail and run history - Edit or delete an automation ## How to use this page ### 1. Understand what an automation does Know what the feature is for before you build one, so the trigger and actions you pick match the follow-up you want. 1. An automation chains **follow-up actions** that run after a call finishes — send a Telegram, WhatsApp, or email message, or call a webhook — without anyone doing it by hand. 2. Each automation has three parts: a **trigger** (the event that starts it, such as an AI call completing), optional **conditions** (rules on the call outcome, IVR responses, or analysis results that must match), and one or more **action steps** (what gets sent). An action step sends on one of five channels — Telegram, WhatsApp, WhatsApp Personal, Email, or a Webhook — and the four message channels send through the accounts you set up on [Messaging connections](/docs/messaging-connections). 3. The same automation is reusable. Attach it to a single call, a bulk dispatch, or a schedule, and it runs for every matching event across those dispatches. 4. Read the **page guide** at the top of the page for a short refresher; use the **Hide page guide** control to collapse it once you are familiar with the feature. ### 2. Review your automations Keep track of what is set up and which automations are live before adding more. 1. Open **Automations** from the sidebar. The table lists every automation in the current tenant with its **Name**, **Trigger**, **Steps** count, **Status** (Enabled or Disabled), **Version**, and when it was **Updated**. Confirm you are in the intended tenant (shown in the top bar) — automations only fire on events within the tenant they belong to. 2. Before you create your first one, the page shows **No automations yet** with a **Create Automation** shortcut instead of the table. 3. Select a row — or its **Run history** action — to open the [automation detail](/docs/automation-detail) page for its summary and run history. Select **Edit** on a row to open the flow in the builder. 4. Use **New Automation** in the top right to start building; this opens the visual builder on a fresh draft. See [Create or edit an automation](/docs/new-automation). ### 3. Delete an automation Remove an automation you no longer need, understanding what happens to runs already under way. 1. Select **Delete** on the automation's row. 2. Confirm in the dialog. It warns that the deletion cannot be undone, that in-flight runs referencing the automation will still complete, and that new dispatches will not fire it. 3. To stop an automation firing without deleting it, edit it and clear its **Status** instead — that keeps the configuration for later. ## Tips and troubleshooting - Start with a narrow trigger, test it, then broaden conditions after confirming the first run behaves correctly. - Use the run drawer or detail page when you need evidence of what happened during an automation run. - An automation only fires on events in the tenant it was created in; switch to the right tenant before you build it. - Every message channel needs a matching messaging connection first (Telegram bot, WhatsApp number, or email domain), so set those up on [Messaging connections](/docs/messaging-connections) before you expect a step to send. ## Related pages - [Create or edit an automation](https://docs.magickvoice.com/docs/new-automation) - [Automation detail](https://docs.magickvoice.com/docs/automation-detail) --- # Create or edit an automation > Build or change a follow-up automation in the visual builder: a flow canvas showing the trigger and its action steps, a settings panel on the right for the selected node, and a Dry-run view that previews what would send against sample or real call data. Creating and editing use the same builder — pick a trigger, add conditions, configure one or more channel steps, preview, then save. - **Section:** Automations - **Audience:** Operations users - **Page address:** `/app/automations/new` ## Common tasks - Name the automation and choose a trigger - Add workflow conditions - Configure each action step and its channel - Preview in Dry-run, then create or save ## How to use this page ### 1. Open the builder Reach the same builder whether you are starting fresh or changing an existing automation. 1. To create one, select **New Automation** on the [Automations](/docs/automations) page. The builder opens with a **Trigger** node and one action step already on the canvas. 2. To change an existing one, select **Edit** on its row (or the **Edit** button on its [detail page](/docs/automation-detail)). The builder opens on the saved flow, using the same canvas, node settings, and Editor / Dry-run tabs. 3. Everything below applies to both. The only difference: a new automation shows **Create** in the header, an existing one shows **Save**. ### 2. Name the automation and pick a trigger Set the identity and the starting event, since the trigger decides which calls the automation reacts to. 1. Select the **Trigger** node (or the empty canvas) to show the automation settings in the right panel. 2. Give it a **Name** (required) so it is easy to find later, and add an optional **Description** for context your teammates will read. 3. Choose the **Trigger** — the event that starts the automation: **After AI call completes**, **After analysis is ready**, **After IVR completes**, or **After announcement completes**. Pick the one that matches the follow-up you want; for example, use *After analysis is ready* when your condition depends on the call's analyzed outcome rather than just that it ended. 4. Leave **Status** set to **Enabled** for the automation to fire on matching events, or clear it to save the automation without it running yet. ### 3. Gate the flow with workflow conditions Decide which calls actually deserve a follow-up, so you do not message everyone who was called. 1. With the trigger node selected, find **Workflow conditions** in the right panel. All conditions here must match before *any* step runs. 2. Leave the operator on **Always** to run for every matching event, or choose an operator to add a rule: comparisons (**=**, **≠**, **>**, **≥**, **<**, **≤**), list membership (**In**, **Not in**), presence (**Exists**, **Missing**), text tests (**Contains**, **Starts with**, **Ends with**), or the logical groups **AND group**, **OR group**, and **NOT** for combining several rules. 3. For a comparison, fill in the **path** and the **value**. The path is a dotted reference to call data — for example `call.status`, `call.talk_time_seconds`, `callee.phone`, `callee.name`, `callee.language`, `callee.metadata.`, or `variables.`. The field suggests the common paths as you type. 4. Once a condition is set, the trigger node on the canvas is labeled **has conditions** so you can see at a glance that the flow is gated. ### 4. Configure an action step Set up what actually gets sent. Each step has one **Channel**, and a step will not fire until its required fields are complete — until then the canvas node is labeled **incomplete**. 1. Select the action step on the canvas to open its settings, then choose a **Channel**. There are five step types: four *message* channels — **Telegram**, **WhatsApp**, **WhatsApp Personal**, and **Email** — and one *request* channel, **Webhook**. Each is defined in its own section below. 2. Fill in the channel's fields (recipient, body, and so on). Text fields accept `{{variable}}` placeholders that are resolved per run from the call context — for example `{{callee.name}}` or `{{call.status}}`. 3. Use the **Variables** section and **+ Add variable** to define named values the step can reuse across its fields. 4. Use **Only run if (per-step condition)** to add a condition that gates just this step, on top of the workflow-level conditions — useful when one step in a chain should only send in a narrower case. It uses the same operators and paths as the workflow conditions. ### 5. How steps connect to messaging connections Understand the link between a step's channel and your messaging setup, because the four message channels can't send until a matching connection exists. 1. A **connection** links MagickVoice to an account it can send through. Message channels reuse the same connections you manage on [Messaging connections](/docs/messaging-connections), so each channel maps to a connection type: **Telegram** → a Telegram bot connection, **WhatsApp** and **WhatsApp Personal** → a WhatsApp connection, and **Email** → a verified email sending domain. 2. When a message step's **Connection** field reads *No connections yet*, use its **Create one** link — it opens [Messaging connections](/docs/messaging-connections) where you add the connection (a Telegram bot token, a Meta Business WhatsApp number, or an email domain). Add it, then return to the builder and pick it. 3. Until a connection is selected, the **To** and **Body** fields stay disabled and the step remains **incomplete**, so it will not send. 4. The **Webhook** channel is the exception — it needs no connection. It posts directly to a URL you supply, so it works without any Messaging setup. ### 6. Step type — Telegram, WhatsApp, and WhatsApp Personal Send the contact a chat message after the call. These three message channels share the same fields. 1. **Connection** (required): the messaging connection to send through — a Telegram bot for Telegram, or a WhatsApp connection for WhatsApp and WhatsApp Personal. See [Messaging connections](/docs/messaging-connections) to set one up. 2. **To** (required): the recipient, defaulting to `{{callee.phone}}` so it messages the person who was called. Change it, or use another `{{variable}}`, to send elsewhere. 3. **Body** (required): the message text. Supports `{{variable}}` placeholders for per-run personalization. 4. Use these when the follow-up is a direct message to the contact — a confirmation, a link, or a next-step prompt right after the call ends. ### 7. Step type — Email Send an email after the call, either free-form or from a saved template. 1. **Connection** (required): an email connection backed by a verified sending domain (managed on [Messaging connections](/docs/messaging-connections)). 2. **To** (required): the recipient address; use `{{callee.email}}` to reach the contact from the call context. 3. **Subject** (required): the email subject line; supports `{{variables}}`. 4. **Template**: optionally choose one of your active email templates (managed on [Messaging templates](/docs/messaging-templates)). The dropdown reads *No active email templates* until you have one. 5. **Body**: used only when no template is selected — supply HTML or plain text, with `{{variables}}` allowed. 6. Use Email for longer or formatted follow-ups, or when you want a consistent branded layout via a template. ### 8. Step type — Webhook Post the call data to your own system instead of messaging a person — for example, to sync an outcome into your CRM. This channel needs no messaging connection. 1. **URL** (required): a public `https://` endpoint that receives the request. Private or internal addresses are rejected — the endpoint must be reachable from the public internet. The URL supports `{{dotted.path}}` variables resolved per run. 2. **Method**: **POST**, **PUT**, or **PATCH**. 3. **Headers**: up to 20 custom request headers; values support `{{variables}}`. `Content-Type` defaults to `application/json`, and the framing headers `Host`, `Content-Length`, `Connection`, and `Transfer-Encoding` are managed for you and cannot be set. 4. **Body**: leave blank to send the default JSON envelope (use the **Default JSON envelope** disclosure to see its shape), or supply your own template with `{{variables}}`. 5. **Signing secret**: optional. Enter one or use **Generate secret**. When set, each request is signed with HMAC-SHA256 and carries `X-Magick-Signature` and `X-Magick-Timestamp` so your receiver can verify the request genuinely came from MagickVoice. Leave it blank to send unsigned requests. 6. Note the **Delivery details** shown in the panel: every request carries `X-Magick-Event`, `X-Magick-Delivery-Id`, and an `Idempotency-Key` (the run id) so your receiver can safely dedupe retries; network errors, 15-second timeouts, and `5xx` responses are retried, while `4xx`, redirects (not followed), and blocked URLs are terminal; each successful send costs 10 millicredits (~0.01 credits). ### 9. Chain multiple steps Build a sequence when one event should trigger more than one follow-up. 1. Select **Add step** on the canvas to append another action. Steps run top to bottom in the order shown. 2. Configure each step's channel independently — for example, post a webhook to your CRM, then send the lead a Telegram confirmation. 3. Use **Duplicate step** to copy a configured step, or **Remove step** to delete one. At least one step is always required, so the remove control is disabled when only one step remains. 4. Give any step its own **Only run if** condition so different steps in the same flow can fire under different circumstances. ### 10. Preview in Dry-run, then save Confirm the flow behaves before it messages real contacts, since a live automation sends to real recipients and spends credits. 1. Switch to the **Dry-run** tab (top right, or the **Dry-run** button in the header). It evaluates the current draft and updates as you edit. 2. Choose a **Context source**: **Sample data** (a built-in example call) or **A recent run** when a real run is available to replay against. 3. Use **Edit context JSON** to inspect or adjust the sample context — the `call`, `callee`, `tenant`, and `account` objects whose fields your conditions and `{{variables}}` read from. 4. Read the result: it reports whether **Workflow conditions matched** and, for each step, whether it would send or was skipped (for example, *Workflow conditions didn't match — no steps would run*). Use **Run locally** to re-evaluate. Nothing is sent and no credits are spent in Dry-run. 5. Select **Create** (new) or **Save** (existing) in the header. If **Status** is enabled, it begins firing on matching events; otherwise it is saved paused until you enable it. After creating, you land on the automation's edit view, and it appears in the [Automations](/docs/automations) list. ### 11. Edit an existing automation safely Treat a change to a live automation as affecting calls from now on, since an enabled automation acts on future matching events the moment you save. 1. Open the automation in the builder with **Edit**, and confirm you have the right one by its **Name** in the right panel. 2. Change the trigger, conditions, or any step as above. Each step re-checks its required fields, so watch for one that flips back to **incomplete**. 3. To stage several changes before any go live, clear **Status** to disable the automation first, make your edits, then re-enable it once the flow is correct. 4. Preview the revised flow in **Dry-run** to confirm it matches — and skips — the calls you expect, then **Save**. Check the next entries in **Run history** on the [detail page](/docs/automation-detail) to confirm it behaves as intended. ## Tips and troubleshooting - Start with a narrow trigger, test it, then broaden conditions after confirming the first run behaves correctly. - Use the run drawer or detail page when you need evidence of what happened during an automation run. - Creating and editing use the same builder; the only difference is that an edit opens on the saved flow. Saving a new automation lands you on its edit view. - Start with a narrow trigger and tight conditions, preview it in Dry-run, then broaden the conditions once the first run behaves the way you expect. - A step stays marked "incomplete" until its required fields are set — a message channel needs a connection and a body; a webhook needs a public https URL — and an incomplete step will not send. - Message channels need a messaging connection to exist first. If a step reports "No connections yet," add one on [Messaging connections](/docs/messaging-connections), then return to the builder. ## Related pages - [Automations](https://docs.magickvoice.com/docs/automations) - [Automation detail](https://docs.magickvoice.com/docs/automation-detail) --- # Automation detail > Review one automation at a glance — its trigger, status, step count, and version — and read its run history for evidence of what happened when it fired. The jump-off point to edit the flow. - **Section:** Automations - **Audience:** Operations users - **Page address:** `/app/automations/:id` ## Common tasks - Check the trigger, status, steps, and version - Read the run history - Open a run for detail - Edit the automation ## How to use this page ### 1. Review an automation at a glance Confirm what an automation is set to do without opening the full builder. 1. Open the detail page by selecting an automation's row on the [Automations](/docs/automations) list, or the **Run history** action on that row. The breadcrumb reads Automations > the automation name, and the name is the page title. 2. Read the summary tiles: **Trigger** (the event it fires on, such as *After AI call completes*), **Status** (**Enabled** or **Disabled**), **Steps** (how many action steps it runs), and **Version** (for example *v1*). 3. Confirm the tenant shown in the top bar matches where the calls happen — an automation only reacts to events within its own tenant. 4. Use **Back** to return to the list, or **Edit** to open the flow in the builder. ### 2. Read the run history Use the run history as evidence of what the automation actually did when events fired. 1. Find the **Run history** section below the summary; the count beside it shows how many runs have been recorded. 2. When the automation has not fired yet — because it is disabled, unattached, or no matching event has occurred — the section reads **No runs yet**, with a note that runs appear once matching events fire and the automation is attached to calls. 3. Once runs exist, review them here to see whether each fired, matched its conditions, and sent — the same outcome the [Dry-run preview](/docs/new-automation) estimates before enabling. ### 3. Decide what to do next Move from reviewing to acting once you know the automation's state. 1. Select **Edit** to change the trigger, conditions, or steps — see [Create or edit an automation](/docs/new-automation). 2. To turn follow-ups on or off without losing the configuration, open it in the builder and toggle **Status**. 3. Check that each message step still points at a live [messaging connection](/docs/messaging-connections) if sends are unexpectedly failing. ## Tips and troubleshooting - Start with a narrow trigger, test it, then broaden conditions after confirming the first run behaves correctly. - Use the run drawer or detail page when you need evidence of what happened during an automation run. ## Related pages - [Automations](https://docs.magickvoice.com/docs/automations) - [Create or edit an automation](https://docs.magickvoice.com/docs/new-automation) --- # Voice messages > Create and manage voice messages — a straight recorded or read-aloud message played to people when they answer your call, with no AI conversation. Type a message we read aloud, or upload your own recording, then send it to a list of numbers from the Campaign Composer. - **Section:** Campaigns - **Audience:** Campaign creators - **Page address:** `/app/announcements` - **Access:** Your admin may need to enable this feature ## Common tasks - Create a typed or recorded voice message - Personalize the message with per-contact fields - Review existing voice messages - Select a voice message for a campaign ## How to use this page ### 1. Understand what a voice message is Know what this feature does before you build one, so you pick it only when a one-way message is what you want. 1. A voice message is a **recorded or typed-aloud message** played to each person when they answer — there is no AI conversation, just a straight message, and the call ends after it plays. 2. There are two types: **Typed** (you write text and we read it aloud in a clear voice) and **Recording** (you upload your own audio file). The table's **Type** column shows which each one is. 3. Once created, a voice message is sent to a list of phone numbers from the **Campaign Composer** — see [New campaign](/docs/new-campaign). The message itself is reusable across many campaigns. 4. Use the **page guide** at the top for a refresher, and **Hide page guide** to collapse it once you are familiar. ### 2. Review your voice messages Keep track of what is set up before creating more or launching a campaign. 1. Open **Voice Messages** from the sidebar. The table lists each message with its **Name**, **Type** (Typed or Recording), **Language**, **Personalized fields**, **Status** (On or off), and **Created** date. 2. Confirm you are in the intended tenant (shown in the top bar) — voice messages belong to the tenant they were created in. 3. Use **Edit** on a row to change a message, or **Delete** to remove one you no longer need. ### 3. Create a typed voice message Write a message we read aloud — the fastest way to send an announcement without recording anything. 1. Select **New voice message**. In the dialog, give it a **Name** (for example *Payment reminder*) so it is easy to find later. 2. Leave **Type** on **Type a message**. 3. In **Message to read aloud**, write what each person should hear. Keep it short and clear. 4. To personalize it, select **Personalize** (or **+ Personalize**) to insert a per-contact field such as the person's name — these are filled in for each recipient at send time from the campaign's contact data. 5. Open **Voice options** to adjust how the message sounds if you want something other than the default clear voice. 6. Select **Create**. The message appears in the list, ready to select in the [Campaign Composer](/docs/new-campaign). ### 4. Create a voice message from a recording Use your own audio when you have a professionally recorded or pre-approved message. 1. First upload the audio on the [Recordings](/docs/recordings) page so it is available to attach. 2. Select **New voice message**, name it, then choose **Upload a recording** under **Type**. 3. Pick the uploaded audio, then **Create**. The message shows **Recording** in the Type column. 4. Use recordings when the exact wording and voice must be consistent — for example a brand message or a legally reviewed script. ## Tips and troubleshooting - Review campaign settings before dispatch because recipient mistakes can be expensive to unwind. - Use analytics after delivery to compare completion, failures, and response trends before sending the next batch. - A voice message is a one-way announcement — the person hears it and the call ends. Use an AI call instead when you need a two-way conversation. - To upload your own audio, add it on [Recordings](/docs/recordings) first, then create a voice message here that points at it. ## Related pages - [Recordings](https://docs.magickvoice.com/docs/recordings) - [Voice message calls](https://docs.magickvoice.com/docs/static-calls) - [New campaign](https://docs.magickvoice.com/docs/new-campaign) - [All campaigns](https://docs.magickvoice.com/docs/all-campaigns) --- # Recordings > Upload and manage the audio files that voice messages and phone menus play. Supported formats are MP3, WAV, OGG, and M4A; each file can be reused across multiple voice messages and phone menus. - **Section:** Campaigns - **Audience:** Campaign creators - **Page address:** `/app/audio-files` - **Access:** Your admin may need to enable this feature ## Common tasks - Upload an audio file - Play a recording to check it - Reuse a recording across campaigns and menus - Delete an unused recording ## How to use this page ### 1. Understand what recordings are for Know how audio files fit into campaigns so you upload them at the right time. 1. Recordings are the **audio files** that a [voice message](/docs/voice-messages) or a [phone menu](/docs/phone-menus) plays when someone answers. 2. A single file can be **reused** across multiple voice messages and menus, so you upload it once and point at it wherever you need it. 3. Supported formats are **MP3, WAV, OGG, and M4A**. Keep recordings short and clear — under 60 seconds works best for an announcement. 4. Use the **page guide** for a refresher, and **Hide page guide** to collapse it. ### 2. Review your recordings See what audio is available before creating a voice message or menu. 1. Open **Recordings** from the sidebar. The table lists each file with its **Name**, **File** name, **Size**, **Duration**, an **ID**, and the **Uploaded** date. 2. Select **Play** on a row to listen and confirm the audio is correct before you use it. 3. Confirm you are in the intended tenant (top bar) — recordings belong to the tenant they were uploaded in. ### 3. Upload an audio file Add a recording so a voice message or phone menu can play it. 1. Select **Upload Audio**. The **Upload Audio File** form appears. 2. Optionally set a **Name** so the file is easy to identify later; otherwise the original file name is used. 3. Choose the audio file. Supported formats are **MP3, WAV, OGG, and M4A**. 4. Select **Upload**. The file appears in the table, ready to attach to a [voice message](/docs/voice-messages) or a [phone menu](/docs/phone-menus). ### 4. Remove a recording Clear out audio you no longer need. 1. Select **Delete** on the recording's row. 2. Deleting removes the file from this list. Make sure it is not still referenced by a voice message or phone menu you rely on before removing it. ## Tips and troubleshooting - Review campaign settings before dispatch because recipient mistakes can be expensive to unwind. - Use analytics after delivery to compare completion, failures, and response trends before sending the next batch. - Keep recordings short and clear — under 60 seconds works best for an announcement. - Upload the audio here first, then attach it to a [voice message](/docs/voice-messages) or a [phone menu](/docs/phone-menus). ## Related pages - [Voice messages](https://docs.magickvoice.com/docs/voice-messages) - [Voice message calls](https://docs.magickvoice.com/docs/static-calls) - [New campaign](https://docs.magickvoice.com/docs/new-campaign) - [All campaigns](https://docs.magickvoice.com/docs/all-campaigns) --- # Voice message calls > The older per-call log for voice message campaigns, showing each recipient with its phone number, campaign, status, carrier, duration, and voice. This page is being retired — new voice message campaigns should be sent from the Campaign Composer — but it remains useful for browsing and exporting historical voice message call records. - **Section:** Campaigns - **Audience:** Campaign creators - **Page address:** `/app/static-calls` - **Access:** Your admin may need to enable this feature ## Common tasks - Review historical voice message calls - Filter by campaign ID or phone number - Export the results to CSV - Move new sends to the Campaign Composer ## How to use this page ### 1. Understand this page Know what this page is so you use the current tool for new sends and keep this one for history. 1. This is the **older voice message call log**. Each row is one recipient of a voice message campaign, with its **Phone**, **Campaign** ID, **Voice message**, **Status** (Connected, No answer, Didn't connect), **Carrier**, **Duration**, **Voice**, and **Time**. 2. A banner at the top notes that **voice message calls have moved to the Campaign Composer** and that this page is being retired soon. For anything new, use **Open the Campaign Composer** or see [New campaign](/docs/new-campaign). 3. The page is still useful for **browsing and exporting** historical voice message call records that were sent before the move. ### 2. Review historical calls Look up past voice message calls and their outcomes. 1. Open the page and read the table. Confirm the tenant in the top bar matches where the calls were made. 2. Use **Filter by campaign ID** to narrow to one campaign, or the **Search phone (exact)** box to find a single recipient — enter the full number with country code, for example `+919876543210`. 3. Read each row's **Status** to see whether the call connected, and **Duration** for how long it played. 4. Use the pager at the bottom to move through pages of results. ### 3. Export the records Take the call data out for reporting or troubleshooting. 1. Select **Export CSV** to download the current results. 2. Use **Customize export columns** to choose which fields the export includes. 3. Keep exports for auditing or to compare against the newer [campaign detail](/docs/campaign-detail) view for campaigns sent from the Composer. ### 4. Move new sends to the Composer Stop using this page for anything new so your work lands in the supported tool. 1. Select **Open the Campaign Composer** on the banner, or go to [New campaign](/docs/new-campaign). 2. Choose the **Voice message** campaign type there — it covers everything this page did, plus AI calls and phone menus, contact lists, scheduling, and cost preview in one place. 3. Track sent campaigns on [All campaigns](/docs/all-campaigns) and open any one for its per-recipient breakdown on [campaign detail](/docs/campaign-detail). ## Tips and troubleshooting - Review campaign settings before dispatch because recipient mistakes can be expensive to unwind. - Use analytics after delivery to compare completion, failures, and response trends before sending the next batch. - This page is being retired. Start new voice message campaigns from the [Campaign Composer](/docs/new-campaign) — it does everything this page did and more. - Use the phone search for an exact match — enter the full number with country code, e.g. +919876543210. ## Related pages - [Voice messages](https://docs.magickvoice.com/docs/voice-messages) - [Recordings](https://docs.magickvoice.com/docs/recordings) - [New campaign](https://docs.magickvoice.com/docs/new-campaign) - [All campaigns](https://docs.magickvoice.com/docs/all-campaigns) --- # New campaign > Send a group of calls in three steps using the Campaign Composer: choose what happens on the call (a voice message, an AI call, or a phone menu), choose who you are calling, then set the sender number and timing. A running summary on the right shows how many people you are reaching and the estimated cost before you send. - **Section:** Campaigns - **Audience:** Campaign creators - **Page address:** `/app/campaigns/new` - **Access:** Your admin may need to enable this feature ## Common tasks - Choose the campaign type - Pick what happens on the call - Add recipients manually or from a contact list - Set the sender number and send now or schedule ## How to use this page ### 1. Pick the campaign type Choose what kind of call this campaign makes, since the rest of the form changes to match. 1. Open the composer with **New Campaign**, **Start a campaign** on the dashboard, or [go straight to it](/docs/all-campaigns) from the Campaigns list. 2. At the top, choose the **Campaign type**: **Voice message** (play a recorded or read-aloud message), **AI call** (an AI agent holds a real conversation with each person), or **IVR Flow** (a phone menu where people press keys). 3. The three steps below adapt to your choice. The **Summary** rail on the right updates live as you fill things in. ### 2. Choose what happens on the call Set the content of the call — this is step 1, and it differs by campaign type. 1. For a **Voice message**, pick one of your [voice messages](/docs/voice-messages) from the list and use **Play preview** to hear it. Manage the messages themselves on the [Voice messages](/docs/voice-messages) page. 2. For an **AI call**, choose the **Call script** the AI follows, then set the **AI quality** tier (**Copper**, **Silver**, **Gold**, **Gold II**, or **Platinum** — higher tiers sound more natural and cost more per minute), and pick a **Voice** and **Language**. Manage scripts on [Call scripts](/docs/call-scripts). 3. For an AI call, also set call handling: **Record these calls** (a small extra charge applies), **Detect answering machines** (so the AI knows whether a person or voicemail picked up), and an optional **Greeting grace period** in seconds so the AI's greeting is not cut off. 4. For an **IVR Flow**, pick the [phone menu](/docs/phone-menus) to run. ### 3. Choose who you're calling Set the recipient list — this is step 2. 1. Choose an input mode: **Enter Manually** to type numbers, or **Use Contact List** to select a saved list. 2. For manual entry, type one number per line. This is capped at **100 numbers per batch**; Indian numbers without `+91` are normalized automatically (for example `9876543210` becomes `+919876543210`). 3. To reach more than 100 recipients, upload them as a [contact list](/docs/contact-lists) and choose **Use Contact List** — lists of any size are supported. 4. If your message or script is personalized, fill in each person's details so the per-contact fields resolve at send time. ### 4. Set the sender and timing Choose the number people see and when the campaign runs — this is step 3. 1. Under **Number people will see**, pick one or more of your [phone numbers](/docs/phone-numbers). When several are selected, they are rotated evenly across recipients; a voice message campaign dials with a single number, so it uses the first one you pick. Filter by provider (for example Vobiz, Telnyx) using the buttons above the list. 2. Optionally set a **Campaign name** so it is easy to find later on [All campaigns](/docs/all-campaigns). 3. Under **Attach automations**, add a compatible [automation](/docs/automations) to run after each call — or **Create one** if none exists yet. 4. Choose a **Scheduling mode**: **Send Now**, or **Schedule for Later** to set a schedule name, date and time, timezone, a status-check interval, and optional retry rules for calls that fail. ### 5. Review the summary and send Confirm what you are about to do before it reaches real people. 1. Read the **Summary** rail: **What people will hear**, **People you're calling** (the recipient count), **Est. cost**, and your **Balance**. 2. The estimated cost is a per-minute **"from ~"** figure — the real cost varies with how long each call lasts. 3. The send button stays disabled (**Not ready yet** / **Add recipients to continue**) until the campaign has recipients and the required fields are set. 4. When everything is set, send the campaign — or save the schedule if you chose **Schedule for Later**. Track it afterward on [All campaigns](/docs/all-campaigns) and open it for the full breakdown on [campaign detail](/docs/campaign-detail). ## Tips and troubleshooting - Review campaign settings before dispatch because recipient mistakes can be expensive to unwind. - Use analytics after delivery to compare completion, failures, and response trends before sending the next batch. - The summary rail on the right shows your recipient count and an estimated cost before you send — check it every time, since a live campaign calls real people and spends credits. - Manual entry is capped at 100 numbers per batch. To reach more, upload a [contact list](/docs/contact-lists) and choose "Use Contact List". - Estimated cost is per-minute, so it is a "from ~" figure — the real cost depends on how long each call lasts. ## Related pages - [Voice messages](https://docs.magickvoice.com/docs/voice-messages) - [Recordings](https://docs.magickvoice.com/docs/recordings) - [Voice message calls](https://docs.magickvoice.com/docs/static-calls) - [All campaigns](https://docs.magickvoice.com/docs/all-campaigns) --- # All campaigns > Track every group of calls you have sent, newest first. Live tiles show what is happening now and what needs a look; the table lists each campaign with its type, how it started, status, progress, contact count, and created date. Open any campaign for its full per-recipient breakdown, stop queued calls, or retry failed calls. - **Section:** Campaigns - **Audience:** Campaign managers - **Page address:** `/app/bulk-dispatch-jobs` - **Access:** Your admin may need to enable this feature ## Common tasks - Scan the live status tiles - Search and filter campaigns - Open a campaign's detail and run history - Stop remaining queued calls - Retry calls that didn't connect ## How to use this page ### 1. Understand this page Know what this page tracks so you can find and monitor your sends. 1. Every row is a **campaign** — one group of calls you sent, whether a voice message, AI call, or phone menu — listed newest first. 2. The tiles across the top summarize live activity: **Happening now**, **People being called**, **On a call now**, and **Needs a look** (campaigns that need attention). 3. When nothing is running, the page reads **All quiet — no campaigns running right now**. 4. Confirm the tenant in the top bar — campaigns belong to the tenant they were sent in. ### 2. Scan live status Get a quick read on what is running before you dig into any one campaign. 1. Read the tiles at the top. **Needs a look** is a button — select it to filter the table straight to campaigns that need attention. 2. The **How it started** column shows whether a campaign was **Created here** (in the Composer) or came **From a contact list**. 3. The **Progress** column shows a breakdown of outcomes (for example connected, no answer, busy, failed, voicemail) with a total. ### 3. Search and filter Narrow a long list to the campaigns you care about. 1. Use **Search by name** to find a campaign by its name. 2. Filter by **status** (Waiting, In progress, Sending, Done, Done — some didn't connect, Couldn't send, Stopped), by **type** (Voice message, AI call, Phone menu, WhatsApp, Telegram), or by a **From / To** date range. 3. Use **More filters** to filter by how a campaign started, and the column headers (Name, Status, Contacts, Created) to sort. 4. **Refresh** re-fetches the latest, and **Views** switches how the list is presented. ### 4. Open a campaign Move from the list to the full detail of one campaign. 1. Select a campaign's row to open its [campaign detail](/docs/campaign-detail) page — its summary, configuration, outcome breakdown, and per-call table. 2. For a running campaign or one with queued calls, use **Stop remaining calls** on the detail page to cancel any pending calls that have not yet started. 3. For a campaign with failures, use the row's **Try the calls that didn't go through** action to retry the recipients that didn't connect. 4. To start a new campaign, go to [New campaign](/docs/new-campaign). ## Tips and troubleshooting - Review campaign settings before dispatch because recipient mistakes can be expensive to unwind. - Use analytics after delivery to compare completion, failures, and response trends before sending the next batch. - The "Needs a look" tile filters straight to campaigns that need attention — start there after a big send. - Campaigns only show for the tenant they were sent in; confirm the tenant in the top bar before assuming a campaign is missing. ## Related pages - [Voice messages](https://docs.magickvoice.com/docs/voice-messages) - [Recordings](https://docs.magickvoice.com/docs/recordings) - [Voice message calls](https://docs.magickvoice.com/docs/static-calls) - [New campaign](https://docs.magickvoice.com/docs/new-campaign) --- # Campaign detail > Inspect one campaign in full: a summary of its type, how it started, people called, and progress; a timeline of created / started / completed; the configuration it ran with; an outcome breakdown of how the calls went; and a per-call table with each recipient's status, duration, sentiment, outcome, and AI summary. Stop remaining queued calls or export the per-call data as a spreadsheet. - **Section:** Campaigns - **Audience:** Campaign managers - **Page address:** `/app/bulk-dispatch-jobs/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Review the campaign summary and timeline - Check the configuration it ran with - Read the outcome breakdown - Stop remaining queued calls - Inspect and export each call ## How to use this page ### 1. Review the campaign at a glance Confirm what a campaign did and when, without reading every call. 1. Open the detail page by selecting a campaign's row on [All campaigns](/docs/all-campaigns). The breadcrumb reads Campaigns > the campaign name, and the name and overall **status** head the page. 2. Read **Campaign details**: **Type** (AI call, Voice message, or Phone menu), **How it started** (Created here or From a contact list), **People called**, and **Progress**. 3. Read the **timeline** — **Created**, **Started**, and **Completed** timestamps — to see how long the run took. 4. Confirm the tenant in the top bar matches where the calls happened. ### 2. Check the configuration See the exact settings the campaign ran with, useful for troubleshooting. 1. Find the **Configuration** section. For an AI call it lists **AI quality**, **Call script**, **Voice**, **Requested language**, **Number people saw**, **Record calls**, **Detect answering machines**, **Greeting grace**, and more. 2. Fields reading **Not recorded** on an older campaign predate settings capture — a note on the page explains those blanks reflect system defaults. 3. Use **Technical details** to expand internal ids, batch counters, and provider/delivery settings. ### 3. Read how the calls went Get the outcome breakdown for the whole campaign at once. 1. Find **How the calls went**. The donut and legend break the total into outcomes — **Connected**, **No answer**, **Line busy**, **Didn't connect**, and **Voicemail** — with a count and percentage each. 2. Use this to judge campaign health at a glance: a high **No answer** share may mean bad timing, while **Didn't connect** points at delivery errors. 3. For trends across many campaigns rather than this one, open [Campaign analytics](/docs/campaign-analytics). ### 4. Stop remaining queued calls Cancel pending calls when a campaign needs to be halted, preventing stranded contacts from receiving unwanted calls. 1. When a campaign is still running or has queued calls waiting to be placed, find the **Stop remaining calls** action near the campaign controls at the top of the detail page. 2. Select **Stop remaining calls** to cancel all calls that are queued but not yet started. This immediately prevents any pending calls from being placed. 3. Use this when a campaign was launched with incorrect settings, when circumstances change and the remaining calls should not proceed, or when queued calls are left hanging after a problem. 4. Already-connected or in-progress calls complete normally; only queued calls waiting to start are canceled. 5. Review the updated progress counts after stopping to confirm how many calls were canceled versus how many had already completed. ### 5. Inspect and export each call Drill into individual recipients when you need the detail. 1. Scroll to **Each call** for the per-recipient table: **Phone**, **Status**, **Duration**, **Talk Time**, **Sentiment**, **Outcome**, **AI summary**, and **Time**. 2. Use the status dropdown to filter to one outcome (for example just **No answer**), and the pager to move through recipients. 3. Select a row to open that individual call, or **Download as spreadsheet** to export the per-call data for reporting. 4. To retry the ones that didn't connect, use the retry action on the campaign's row back on [All campaigns](/docs/all-campaigns). ## Tips and troubleshooting - Review campaign settings before dispatch because recipient mistakes can be expensive to unwind. - Use analytics after delivery to compare completion, failures, and response trends before sending the next batch. - The "How the calls went" chart is the fastest read on a campaign — connected vs. no answer, busy, didn't connect, and voicemail, as counts and percentages. - Older campaigns may show "Not recorded" for some configuration fields; those predate settings capture and reflect system defaults. ## Related pages - [Voice messages](https://docs.magickvoice.com/docs/voice-messages) - [Recordings](https://docs.magickvoice.com/docs/recordings) - [Voice message calls](https://docs.magickvoice.com/docs/static-calls) - [New campaign](https://docs.magickvoice.com/docs/new-campaign) --- # Campaign analytics > Visualize the performance of your bulk call campaigns across your recent calls. Charts show the distribution of announcements used, call statuses, providers, and call duration over time, so you can spot what is working and improve the next send. Chart sizes are resizable and your layout is saved automatically. - **Section:** Campaigns - **Audience:** Campaign managers - **Page address:** `/app/campaign-analytics` - **Access:** Your admin may need to enable this feature ## Common tasks - Review outcome and status distribution - Compare providers and announcements - Read call duration over time - Apply findings to the next campaign ## How to use this page ### 1. Understand what analytics shows Know the scope of this page so you read the charts correctly. 1. The page visualizes the performance of your **bulk call campaigns** across your most recent calls (the header notes the sample, for example *Last 37 bulk calls*). 2. Four charts summarize the data: **Announcement Distribution** (which voice messages were used), **Status Distribution** (how the calls ended), **Provider Distribution** (which carriers carried the calls), and **Call Duration Over Time**. 3. This is the cross-campaign trend view; for one campaign's outcomes, use its [campaign detail](/docs/campaign-detail) page instead. 4. Confirm the tenant in the top bar — analytics cover the tenant you are in. ### 2. Read the charts Turn the charts into decisions about your calling. 1. Use **Status Distribution** to see how calls ended overall — a large share of no-answers or failures signals a timing or delivery problem worth fixing. 2. Use **Provider Distribution** to compare carriers, and **Announcement Distribution** to see which messages you have been sending most. 3. Use **Call Duration Over Time** to spot whether calls are getting longer or shorter across recent sends. 4. Select **Refresh campaign analytics** to pull the latest data. ### 3. Adjust the layout Arrange the charts to suit how you review them. 1. Drag a chart's edge to resize it. Your layout is saved automatically. 2. Select **Reset Layout** to return to the default chart sizes. ### 4. Apply the findings Close the loop by feeding what you learn back into your next send. 1. If status distribution shows many no-answers, adjust timing on your next [campaign](/docs/new-campaign) or use **Schedule for Later** to call at a better hour. 2. If one provider underperforms, choose a different **Number people will see** in the Composer, since that sets which provider carries the calls. 3. Compare against a single campaign's [outcome breakdown](/docs/campaign-detail) to confirm whether a trend is one bad campaign or a broader pattern. ## Tips and troubleshooting - Review campaign settings before dispatch because recipient mistakes can be expensive to unwind. - Use analytics after delivery to compare completion, failures, and response trends before sending the next batch. - Charts cover your most recent bulk calls, so they reflect recent activity rather than an arbitrary date range. - Drag a chart's edge to resize it — your layout is saved automatically, and Reset Layout restores the defaults. ## Related pages - [Voice messages](https://docs.magickvoice.com/docs/voice-messages) - [Recordings](https://docs.magickvoice.com/docs/recordings) - [Voice message calls](https://docs.magickvoice.com/docs/static-calls) - [New campaign](https://docs.magickvoice.com/docs/new-campaign) --- # Messaging connections > Connect and manage the messaging accounts MagickComms sends through — a WhatsApp Business number, a Telegram bot, an email sending domain, or a linked personal WhatsApp number — and monitor each connection's send, delivery, and failure counts. - **Section:** Messaging - **Audience:** Messaging operators - **Page address:** `/app/messaging/connections` - **Access:** Your admin may need to enable this feature ## Common tasks - Add a connection - Review connection health and status - Copy a connection's invite link - Edit or revoke a connection ## How to use this page ### 1. Understand what a connection is Know what connections do before adding one, because messaging cannot happen without at least one. 1. A connection links MagickComms to one place it can send from — a WhatsApp phone number, a Telegram bot, or an email sending domain. The page guide summarizes this at the top. 2. You need at least one active connection before you can send messages. Both [automations](/docs/automations) and direct [message](/docs/messages) sends deliver through the connections managed here. 3. Note the prerequisites per provider: WhatsApp connections require a Meta Business phone number; Telegram connections require a bot token from @BotFather; email connections require a verified sending domain. 4. WhatsApp and Email sends use approved [messaging templates](/docs/messaging-templates), so set up the matching connection here first, then author templates against it. ### 2. Read the connections list Check the health of every connection at a glance and find the one you need. 1. Open Connections. The count beside the heading shows how many connections exist, and the table lists one row per connection. 2. Read across the columns: Provider (WhatsApp, Telegram, or Email), Name, the connection's address (Phone / Bot / Domain), the Sent / Delivered / Read counts, the Failed count, Status, and Created date. 3. Check Status to confirm a connection is usable — for example, "Active — Currently running and operational" means it is running and can send. 4. Select any row to open its [connection detail](/docs/messaging-connection-detail) page for the full connection information, stats, and provider-specific setup such as an invite link or QR code. ### 3. Add a connection Create a new connection when you need a new sending identity or channel. 1. Select Add Connection to open the provider picker dialog. It shows four cards: WhatsApp Business ("Connect a Meta WhatsApp Business phone number to send template messages"), Telegram Bot ("Connect a Telegram bot to send messages to users who interact with it"), Email (Resend) ("Send bulk campaign emails via Resend. Verify your sending domain"), and WhatsApp Personal ("Link a personal WhatsApp number via QR code and send free-text messages"). 2. Choose the card for the channel you want. Each opens a form with the fields that provider needs, described in the sections below. 3. Fill in the required fields and select Create, or Cancel to close without adding. The new connection appears in the list. 4. After creating, open the connection's [detail page](/docs/messaging-connection-detail) to finish any provider-specific setup — for WhatsApp Personal, scanning the QR code to link the account; for Email, completing DNS verification of the domain. ### 4. Add a Telegram connection Connect a Telegram bot so it can message users who interact with it. 1. On the Telegram card, select it, then enter a Connection Name (for example, "Support Bot") to identify it in the list. 2. Enter the Bot Token obtained from @BotFather. 3. Optionally set a Welcome Message — the message sent when a user first starts the bot — and a Contact Shared Message, sent when a user shares their contact. 4. Select Create. The connection's detail page then provides an invite link to share with customers so they can start the bot and share their phone number. ### 5. Add a WhatsApp Business connection Connect a Meta WhatsApp Business phone number for template-based messaging. 1. Enter a Connection Name (for example, "Production WhatsApp"). 2. Enter the Phone Number ID (the Meta Phone Number ID) and, optionally, the Display Phone Number shown to recipients. 3. Optionally enter the Business Account ID (the WhatsApp Business Account ID), which is needed for template sync. 4. Enter the Access Token (Meta API access token) and the App Secret (Meta App Secret), then select Create. Use approved [messaging templates](/docs/messaging-templates) to send through this connection. ### 6. Add an Email connection Connect a verified sending domain to send campaign emails via Resend. 1. Enter a Connection Name (for example, "Collections Email"). 2. Enter the Sending Domain (for example, "mail.acme-collections.com") — the domain you want to send emails from. DNS records will be generated for verification. 3. Set the From Name (for example, "Acme Collections") and the From Email (for example, "collections@mail.acme-collections.com"), and optionally a Reply-To Email. 4. Select Create. Complete the DNS verification for the domain, then send using your [messaging templates](/docs/messaging-templates). ### 7. Add a WhatsApp Personal connection Link a personal WhatsApp number by QR code to send free-text messages. 1. Enter a Connection Name (for example, "My WhatsApp"). 2. Note the on-screen message: after creating, you will be taken to the connection page to scan a QR code and link your WhatsApp account. 3. Select Create. 4. On the [connection detail](/docs/messaging-connection-detail) page, scan the QR code with the WhatsApp app on the phone you are linking to complete the connection. ### 8. Manage an existing connection Keep connections current and remove ones you no longer use. 1. Use Copy invite link on a row to copy the connection's share link — most useful for Telegram, where customers use it to start the bot. 2. Use Edit on a row to change a connection's settings, such as its name or credentials. 3. Use Revoke on a row to disable a connection you no longer want to send through. Confirm it is not still used by an [automation](/docs/automations) or a pending [message](/docs/messages) send before revoking it. ## Tips and troubleshooting - Keep connection health visible before sending important messages; disconnected accounts cannot deliver reliably. - Open the message detail page for delivery evidence, payload review, and troubleshooting context. ## Related pages - [Messaging connection detail](https://docs.magickvoice.com/docs/messaging-connection-detail) - [Messaging templates](https://docs.magickvoice.com/docs/messaging-templates) - [Messages](https://docs.magickvoice.com/docs/messages) - [Message detail](https://docs.magickvoice.com/docs/message-detail) --- # Messaging connection detail > Inspect one messaging connection — its provider settings, live status, and message counts — and complete provider-specific setup such as sharing a Telegram invite link, scanning a WhatsApp Personal QR code, or verifying an email domain. - **Section:** Messaging - **Audience:** Messaging operators - **Page address:** `/app/messaging/connections/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Review connection status and information - Read the sent and failed message counts - Copy and share the invite link - Edit or revoke the connection ## How to use this page ### 1. Review the connection Confirm a connection's identity and state before relying on it to send. 1. Open the page by selecting a row on [Messaging connections](/docs/messaging-connections). The breadcrumb reads Connections > the connection name, and the title is the connection's name. 2. Read the Status pill beside the title — for example, "Active — Currently running and operational" means the connection is running and can send. 3. Use Edit to change the connection's settings, or Revoke to disable it. Confirm the connection is not still used by an [automation](/docs/automations) or a pending [message](/docs/messages) send before revoking it. ### 2. Read the connection information Check the provider settings recorded for this connection. 1. Find the Connection Information section, which lists the details specific to the provider. For a Telegram connection this shows the Bot Username (a t.me link), the Bot Display Name, the Created timestamp, and the Last Used timestamp. 2. A WhatsApp or Email connection shows the settings for its provider instead — the phone number or the sending domain that identifies the connection. 3. Use these details to verify the connection points at the account you expect before sending through it. ### 3. Check the message counts See how much this connection has sent and whether anything is failing. 1. Read the stat tiles: Messages Sent shows the total messages sent through the connection, and Messages Failed shows how many did not go through. 2. A rising Messages Failed count is the signal to open Edit and check the connection's credentials or status. 3. For the fuller send, delivery, and read breakdown across all connections, return to the [connections list](/docs/messaging-connections). ### 4. Onboard customers (Telegram) Bring customers onto a Telegram bot so it can message them. 1. In the Customer Onboarding section, find the copyable invite link — for example, https://t.me/?start=ref — and use the Copy button to copy it. 2. Share the link with your customers. When they open it, Telegram prompts them to start your bot and share their phone number. 3. Watch the counter showing how many contacts have shared their phone number to track onboarding progress. ### 5. Finish setup for other providers Complete the provider-specific step that makes a non-Telegram connection usable. 1. For a WhatsApp Personal connection, scan the QR code shown on this page with the WhatsApp app on the phone you are linking, to connect the account. 2. For an Email connection, verify the sending domain by adding the generated DNS records; the connection can send once the domain is verified. 3. Once setup is complete and the Status reads active, the connection is ready for [automations](/docs/automations) and [message](/docs/messages) sends. WhatsApp and Email sends use your approved [messaging templates](/docs/messaging-templates). ## Tips and troubleshooting - Keep connection health visible before sending important messages; disconnected accounts cannot deliver reliably. - Open the message detail page for delivery evidence, payload review, and troubleshooting context. ## Related pages - [Messaging connections](https://docs.magickvoice.com/docs/messaging-connections) - [Messaging templates](https://docs.magickvoice.com/docs/messaging-templates) - [Messages](https://docs.magickvoice.com/docs/messages) - [Message detail](https://docs.magickvoice.com/docs/message-detail) --- # Messaging templates > Review and manage the pre-approved WhatsApp message templates used for outbound messaging, sync approved templates from Meta, or create a new one for approval. Templates can include images, videos, and documents from the media library. - **Section:** Messaging - **Audience:** Messaging operators - **Page address:** `/app/messaging/templates` - **Access:** Your admin may need to enable this feature ## Common tasks - Review templates and their approval status - Sync templates from Meta - Create a template manually - Add media to templates - Use a template when sending or in an automation ## How to use this page ### 1. Understand what templates are for Know why templates exist before you manage them, because they only matter for some channels. 1. Open Message Templates. The page lists your WhatsApp message templates — pre-approved message formats that Meta requires. You can only send WhatsApp messages using formats that Meta has approved. 2. Note the channel scope: templates are used for **WhatsApp and Email** messages. **Telegram** messages use free-form text, so you compose them directly when sending and no template is needed. 3. Read the page guide, which explains the essentials: templates are created and submitted for approval through Meta's Business Manager; only templates with **Approved** status can be used to send; and templates can include `{{variables}}` that are replaced with personalized values when sending. 4. Sending an actual message also needs a live connection. Set up the WhatsApp or Email account first on [Messaging connections](/docs/messaging-connections). ### 2. Review your templates and their status Confirm a template is ready before you rely on it, since only approved templates can send. 1. Scan the list for the template you need. Each template carries a status from Meta — a template must be **Approved** before it can be used to send a message. 2. If you have no templates yet, the page shows an empty state — "No WhatsApp templates yet" — with two ways forward: sync templates from Meta, or create one manually. 3. Check the template's language and category so you pick the right variant when sending, and note which `{{variables}}` it expects so you can supply their values. ### 3. Sync templates from Meta Pull in templates you already created and got approved in Meta's Business Manager, so you do not have to recreate them here. 1. Use the sync option from the Message Templates page to fetch your existing templates from Meta's Business Manager. 2. Synced templates arrive with the status Meta has assigned them — only the ones marked **Approved** are usable for sending. 3. Sync again whenever you approve or change templates in Business Manager so the list here stays current. ### 4. Create a template manually Draft a new template here and submit it for Meta approval, when you would rather build it in MagickVoice than in Business Manager. 1. Select **Create** (top right, or the button in the empty state) to open the **Create Template** dialog. 2. Enter a **Template Name** using lowercase letters, numbers, and underscores only (for example `payment_reminder`) — the helper text and `lowercase_with_underscores` placeholder show the required format. 3. Choose a **Language**. It defaults to **English (US)** and offers a wide range of languages, including English (UK), Hindi, Telugu, Tamil, Spanish, Portuguese (BR), Arabic, French, and German. 4. Pick a **Category**: **Utility** (the default), **Marketing**, or **Authentication**. Match it to the message's purpose, as Meta reviews templates against their category. 5. Optionally add **Header Text** for a short heading or select **Add Media** to include an image, video, or document in the template header. Media is uploaded to and managed through the media library. 6. Write the **Body Text**. WhatsApp templates use numbered, positional variables — `{{1}}`, `{{2}}`, `{{3}}` — that are filled in when sending, as in "Hello {{1}}, your payment of {{2}} is due on {{3}}." 7. Optionally add **Footer Text**, such as "Reply STOP to unsubscribe." Select **Create** to submit the template, or **Cancel** to discard it. ### 5. Add media to a template Include images, videos, or documents in WhatsApp templates to make messages richer and more engaging. 1. When creating or editing a template, find the **Header** section and select **Add Media** instead of entering header text. 2. Choose the media type you want to include: **Image**, **Video**, or **Document**. Each template can include one piece of media in its header. 3. Upload the file from your device or select one from the media library. The media library stores all uploaded files so you can reuse them across multiple templates and campaigns. 4. Use the media library to organize and manage your files — remove unused media, add new files, and review what is available for templates and campaigns. 5. When sending a message with this template, the media is delivered as part of the WhatsApp message automatically. Recipients see the image, video, or document at the top of the message. ### 6. Use an approved template Put a template to work once Meta has approved it, so your outbound messages use a sanctioned format. 1. Confirm the template shows **Approved** status here, and that the matching WhatsApp or Email connection exists on [Messaging connections](/docs/messaging-connections). 2. When sending, choose the approved template and supply values for its `{{1}}`, `{{2}}` positional variables so each recipient gets a personalized message. 3. Automations can send from an active template too: an Email step in the automation builder lets you select an active template — see [New automation](/docs/new-automation) and the [Automations](/docs/automations) overview. 4. For Telegram follow-ups, skip templates entirely and compose the message text directly when sending. ## Tips and troubleshooting - Keep connection health visible before sending important messages; disconnected accounts cannot deliver reliably. - Open the message detail page for delivery evidence, payload review, and troubleshooting context. ## Related pages - [Messaging connections](https://docs.magickvoice.com/docs/messaging-connections) - [Messaging connection detail](https://docs.magickvoice.com/docs/messaging-connection-detail) - [Messages](https://docs.magickvoice.com/docs/messages) - [Message detail](https://docs.magickvoice.com/docs/message-detail) --- # Messages > Send and review outbound messages, delivery state, and follow-up message activity. - **Section:** Messaging - **Audience:** Messaging operators - **Page address:** `/app/messaging/messages` - **Access:** Your admin may need to enable this feature ## Common tasks - Send a message - Filter message history - Open message detail - Start follow-up from context ## How to use this page ### 1. Use this page to connect channels and manage messages Understand what is available on Messages and choose the right next action. 1. Open Messages from the Messaging area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Keep connection health visible before sending important messages; disconnected accounts cannot deliver reliably. - Open the message detail page for delivery evidence, payload review, and troubleshooting context. ## Related pages - [Messaging connections](https://docs.magickvoice.com/docs/messaging-connections) - [Messaging connection detail](https://docs.magickvoice.com/docs/messaging-connection-detail) - [Messaging templates](https://docs.magickvoice.com/docs/messaging-templates) - [Message detail](https://docs.magickvoice.com/docs/message-detail) --- # Message detail > Review a single message, including recipient, channel, template, payload, delivery state, and error context. - **Section:** Messaging - **Audience:** Messaging operators - **Page address:** `/app/messaging/messages/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Review message payload - Inspect delivery status - Troubleshoot failed delivery - Open related thread ## How to use this page ### 1. Use this page to connect channels and manage messages Understand what is available on Message detail and choose the right next action. 1. Open Message detail from the Messaging area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Keep connection health visible before sending important messages; disconnected accounts cannot deliver reliably. - Open the message detail page for delivery evidence, payload review, and troubleshooting context. ## Related pages - [Messaging connections](https://docs.magickvoice.com/docs/messaging-connections) - [Messaging connection detail](https://docs.magickvoice.com/docs/messaging-connection-detail) - [Messaging templates](https://docs.magickvoice.com/docs/messaging-templates) - [Messages](https://docs.magickvoice.com/docs/messages) --- # Schedules > View every one-time scheduled campaign — calls and messages set to go out at a future date and time. Schedules are created from the Campaign Composer or the Messages page by choosing "Schedule for Later"; this page lists them with their type, status, and planned time, and lets you open one for contact-level outcomes or cancel it before it runs. - **Section:** Scheduling - **Audience:** Campaign schedulers - **Page address:** `/app/schedules` - **Access:** Your admin may need to enable this feature ## Common tasks - Review upcoming one-time sends - Filter by status and type - Open a schedule for contact outcomes - Cancel a schedule before it runs ## How to use this page ### 1. Understand what a schedule is Know what this page tracks so you look in the right place. 1. A schedule is a **one-time campaign set to go out at a future date and time** — calls or messages that have not run yet. 2. Schedules are **created elsewhere**: from the [Campaign Composer](/docs/new-campaign) (AI voice, voice message, or IVR calls) or from Messages (WhatsApp/Email), by choosing **Schedule for Later**. This page is where you review and manage them. 3. Each schedule shows its **type** (AI Voice, IVR, Static Call, or WhatsApp), its **status**, and its planned time. 4. For repeating sends on a daily, weekly, or monthly cadence, use [Recurring schedules](/docs/recurring-schedules) instead. ### 2. Review and filter schedules Find the scheduled send you care about. 1. Open **Schedules** from the sidebar. Confirm the tenant in the top bar — schedules belong to the tenant they were created in. 2. Filter by **status** — Scheduled, Executing, Completed, Partially Failed, Failed, or Cancelled — using the first dropdown. 3. Filter by **type** — AI Voice, IVR, Static Call, or WhatsApp — using the second dropdown. 4. Select **Refresh** to pull the latest state. 5. Before anything is scheduled, the page shows **No schedules found** with an **Open the Campaign Composer** shortcut. ### 3. Open or cancel a schedule Move from the list to one schedule, or stop it before it runs. 1. Select a schedule to open its [schedule detail](/docs/schedule-detail) page, where you can see individual contact outcomes and retry history. 2. To stop a scheduled campaign that has not started yet, cancel it — you can cancel any time before it begins executing. 3. To create a new scheduled send, go to the [Campaign Composer](/docs/new-campaign) and choose **Schedule for Later**. ## Tips and troubleshooting - Use recurring schedules for repeating operational sends, not one-off campaigns. - Review upcoming instances after editing a recurring schedule so you know which future sends changed. - Schedules are created from a call or messaging page — choose "Schedule for Later" there. This page is where you track and manage them afterward. - You can cancel a scheduled campaign any time before it starts executing. ## Related pages - [Schedule detail](https://docs.magickvoice.com/docs/schedule-detail) - [Recurring schedules](https://docs.magickvoice.com/docs/recurring-schedules) - [New recurring schedule](https://docs.magickvoice.com/docs/new-recurring-schedule) - [Edit recurring schedule](https://docs.magickvoice.com/docs/edit-recurring-schedule) --- # Schedule detail > Inspect one scheduled campaign — its timing, recipients, and the content it will send — and, once it has run, the individual contact outcomes and retry history. The place to confirm a scheduled send is set up correctly, or to review how it went. - **Section:** Scheduling - **Audience:** Campaign schedulers - **Page address:** `/app/schedules/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Review the schedule's timing and status - Check recipients and content - Read contact-level outcomes after it runs - Review retry history ## How to use this page ### 1. Review the scheduled send Confirm what a schedule will do, and when, before it runs. 1. Open the detail page by selecting a schedule on the [Schedules](/docs/schedules) list. 2. Review the schedule's **timing** (the planned date, time, and timezone) and its current **status** — for example Scheduled, Executing, Completed, or Cancelled. 3. Check the **recipients** and the **content** it will send — the voice message, AI call script, phone menu, or message — so you know it is set up the way you intended. 4. Confirm the tenant in the top bar matches where the calls or messages should go. ### 2. Read outcomes after it runs Use the detail page as evidence once the scheduled send has executed. 1. After the schedule fires, review the **individual contact outcomes** — whether each recipient connected, and how the call or message ended. 2. Check the **retry history** for any recipients the system retried after a failure. 3. For an overview across many sends rather than this one, open [Campaign analytics](/docs/campaign-analytics); for the campaign's full per-call breakdown, see its [campaign detail](/docs/campaign-detail). ### 3. Manage the schedule Act on the schedule from its detail page. 1. To stop a scheduled campaign that has not started, **cancel** it — you can cancel any time before it begins executing. 2. To set up repeating sends instead of a single future run, create a [recurring schedule](/docs/new-recurring-schedule). 3. Return to the [Schedules](/docs/schedules) list to review your other scheduled sends. ## Tips and troubleshooting - Use recurring schedules for repeating operational sends, not one-off campaigns. - Review upcoming instances after editing a recurring schedule so you know which future sends changed. - A scheduled send does not run until its planned time — until then this page shows what will happen rather than results. - Cancel a schedule from here (or the list) before it starts executing if you need to stop it. ## Related pages - [Schedules](https://docs.magickvoice.com/docs/schedules) - [Recurring schedules](https://docs.magickvoice.com/docs/recurring-schedules) - [New recurring schedule](https://docs.magickvoice.com/docs/new-recurring-schedule) - [Edit recurring schedule](https://docs.magickvoice.com/docs/edit-recurring-schedule) --- # Recurring schedules > Automate outreach with schedules that repeat on a daily, weekly, or monthly cadence with no manual intervention. Each recurrence creates a one-time schedule instance you can track individually; pause a schedule to stop it temporarily, then resume when ready. - **Section:** Scheduling - **Audience:** Campaign schedulers - **Page address:** `/app/recurring-schedules` - **Access:** Your admin may need to enable this feature ## Common tasks - Create a recurring schedule - Filter by status and frequency - Open a schedule's execution history - Pause, resume, or cancel a schedule ## How to use this page ### 1. Understand recurring schedules Know how repeating schedules work before you build one. 1. A recurring schedule sends calls or messages **automatically on a daily, weekly, or monthly cadence** — no manual step each time. 2. **Each recurrence creates a one-time schedule instance** that you can track individually, so the recurring schedule acts as a template that keeps producing runs. 3. You can **pause** a schedule to stop it temporarily and **resume** it later, or **cancel** it permanently so no future instances are created. 4. For a single future send rather than a repeating one, use a one-time [schedule](/docs/schedules) from the Composer instead. ### 2. Review your recurring schedules See what is automated before adding more. 1. Open **Recurring** from the sidebar. Confirm the tenant in the top bar — schedules belong to the tenant they were created in. 2. Filter by **status** (Active, Paused, Cancelled) or by **frequency** (Daily, Weekly, Monthly) using the dropdowns. 3. Each row shows the schedule's name, type, cadence, status, run count, and last run. Select **Refresh** to update. 4. Before you create your first one, the page shows **No recurring schedules** with a **Create Recurring Schedule** shortcut. ### 3. Create or open a schedule Start a new recurring schedule, or drill into an existing one. 1. Select **Create** (or **Create Recurring Schedule** on the empty state) to open the builder — see [New recurring schedule](/docs/new-recurring-schedule). 2. Select any schedule's row to open its [recurring schedule detail](/docs/recurring-schedule-detail), where you can read its configuration and execution history and drill into individual runs. 3. From the detail page you can **Edit**, **Pause** or resume, or **Cancel** the schedule. ## Tips and troubleshooting - Use recurring schedules for repeating operational sends, not one-off campaigns. - Review upcoming instances after editing a recurring schedule so you know which future sends changed. - Each recurrence creates a one-time schedule instance — so a recurring schedule is a template that keeps producing runs on its cadence. - Pause a recurring schedule to stop it temporarily without losing its configuration, then resume when you are ready. ## Related pages - [Schedules](https://docs.magickvoice.com/docs/schedules) - [Schedule detail](https://docs.magickvoice.com/docs/schedule-detail) - [New recurring schedule](https://docs.magickvoice.com/docs/new-recurring-schedule) - [Edit recurring schedule](https://docs.magickvoice.com/docs/edit-recurring-schedule) --- # New recurring schedule > Create a recurring schedule in one form: name it and pick a type (AI Voice, IVR, Static Call, or WhatsApp), set the repeat cadence (daily, weekly, or monthly) with a time and timezone, choose recipients manually or from a contact list, configure the call or message content, and optionally enable retries. The call configuration section changes to match the type you pick. - **Section:** Scheduling - **Audience:** Campaign schedulers - **Page address:** `/app/recurring-schedules/new` - **Access:** Your admin may need to enable this feature ## Common tasks - Name the schedule and pick a type - Set the repeat cadence, time, and timezone - Choose recipients and content - Enable retries, then create ## How to use this page ### 1. Name the schedule and pick a type Set the identity and communication type first, since the content section adapts to it. 1. Open the builder with **Create** on the [Recurring schedules](/docs/recurring-schedules) page. 2. Under **Basic Configuration**, give the schedule an optional **Name** (for example *Daily customer check-in*). 3. Choose the **Schedule Type**: **AI Voice Call**, **IVR Call**, **Static Call** (voice message), or **WhatsApp Message**. The **Call Configuration** section further down changes to match. ### 2. Set the recurrence Decide how often the schedule runs and when. 1. In **Recurrence**, choose a **Frequency**: **Daily**, **Weekly**, or **Monthly**. 2. Set the **Time** and **Timezone** the schedule fires at. 3. For **Weekly**, pick the **Days of Week** it should run; for **Monthly**, set the **Day of Month**. 4. Set a **Start Date**, and optionally an **End Date** — leave the end date blank to run indefinitely. ### 3. Choose recipients Set who each run reaches. 1. In **Contacts**, choose **Enter Manually** to type numbers, or **Use Contact List** to select a saved [contact list](/docs/contact-lists). 2. Prefer a contact list for dynamic recipients: **the list is re-read on every recurrence**, so contacts you add to it later are picked up automatically without editing the schedule. 3. The selected list shows its contact count and columns, with a link to view the full preview. ### 4. Configure the content and retries Set what each run sends, and how failures are handled. 1. In **Call Configuration**, fill the fields for your type — for a voice message (Static Call) that is the **Announcement** and the **Caller ID**; other types show their own required fields. Advanced users can use **Edit as JSON**. 2. Under **Retry Configuration**, optionally **Enable retry on failure** so the system automatically retries calls that fail (for example no answer or busy). 3. Select **Create Recurring Schedule**. You land on the schedule's [detail page](/docs/recurring-schedule-detail), and it appears in the [Recurring schedules](/docs/recurring-schedules) list. ## Tips and troubleshooting - Use recurring schedules for repeating operational sends, not one-off campaigns. - Review upcoming instances after editing a recurring schedule so you know which future sends changed. - Pick a schedule type first — the call configuration section below changes based on your choice. - Use a contact list for dynamic recipients — the list is re-read on every run, so contacts you add later are picked up automatically. ## Related pages - [Schedules](https://docs.magickvoice.com/docs/schedules) - [Schedule detail](https://docs.magickvoice.com/docs/schedule-detail) - [Recurring schedules](https://docs.magickvoice.com/docs/recurring-schedules) - [Edit recurring schedule](https://docs.magickvoice.com/docs/edit-recurring-schedule) --- # Edit recurring schedule > Update a recurring schedule using the same form as creation — change its name, cadence, recipients, content, or retry settings. Changes apply to future runs only; the schedule type and start date are fixed after creation and cannot be changed here. - **Section:** Scheduling - **Audience:** Campaign schedulers - **Page address:** `/app/recurring-schedules/:id/edit` - **Access:** Your admin may need to enable this feature ## Common tasks - Change the cadence, time, or timezone - Update recipients or content - Adjust retry settings - Save changes for future runs ## How to use this page ### 1. Open the schedule for editing Reach the edit form from the schedule you want to change. 1. Open the schedule's [detail page](/docs/recurring-schedule-detail) from the [Recurring schedules](/docs/recurring-schedules) list, then select **Edit**. 2. The form is the same one used to [create a schedule](/docs/new-recurring-schedule), pre-filled with the current settings. 3. Confirm you have the right schedule by its **Name** at the top before making changes. ### 2. Change what you can Update the settings that are still editable after creation. 1. Change the **Recurrence** — frequency, time, timezone, and (for weekly or monthly) the days — and the optional **End Date**. 2. Update the **Contacts** (manual numbers or the [contact list](/docs/contact-lists), which is still re-read on each future run) and the **Call Configuration** content. 3. Adjust **Retry Configuration**. Retry changes apply to **future failures only**. 4. Note the fixed fields: **Schedule Type** and **Start Date** are disabled and cannot be changed after creation. ### 3. Save the changes Apply your edits to future runs. 1. Select **Save Changes**. Changes apply to **future scheduled runs** — instances that already fired are unaffected. 2. Back on the [detail page](/docs/recurring-schedule-detail), confirm the updated configuration and watch the next entries in **Execution History**. 3. To stop the schedule instead of editing it, **Pause** it (temporarily) or **Cancel** it (permanently) from the detail page. ## Tips and troubleshooting - Use recurring schedules for repeating operational sends, not one-off campaigns. - Review upcoming instances after editing a recurring schedule so you know which future sends changed. - Schedule type and start date are fixed after creation — everything else can be changed. - Changes apply to future runs only; instances that already fired are unaffected, and retry changes apply to future failures only. ## Related pages - [Schedules](https://docs.magickvoice.com/docs/schedules) - [Schedule detail](https://docs.magickvoice.com/docs/schedule-detail) - [Recurring schedules](https://docs.magickvoice.com/docs/recurring-schedules) - [New recurring schedule](https://docs.magickvoice.com/docs/new-recurring-schedule) --- # Recurring schedule detail > Review one recurring schedule at a glance — its status, type, cadence, timezone, start and end dates, retry setting, run counts, last run, and next fire — and read its execution history. The jump-off point to edit, pause, resume, or cancel the schedule. - **Section:** Scheduling - **Audience:** Campaign schedulers - **Page address:** `/app/recurring-schedules/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Read the recurrence configuration - Check run counts and next fire - Review execution history - Edit, pause, resume, or cancel ## How to use this page ### 1. Review the schedule at a glance Confirm what a recurring schedule is set to do without opening the editor. 1. Open the detail page by selecting a schedule's row on the [Recurring schedules](/docs/recurring-schedules) list. The breadcrumb reads Recurring Schedules > the schedule name. 2. Read the **Recurrence Configuration** grid: **Status** (Active, Paused, or Cancelled), **Schedule Type**, **Frequency**, the human-readable **Recurrence** (for example *Every day at 09:00*), **Timezone**, **Start Date**, **End Date** (or *Indefinite*), and **Retry**. 3. Check the run counters: **Total Runs**, **Last Run** (or *Never*), **Next Fire**, and **Created**. 4. Confirm the tenant in the top bar matches where the calls or messages should go. ### 2. Read the execution history Use the history as evidence of what the schedule actually did. 1. Find the **Execution History** section; the count beside it shows how many instances have run. 2. When the schedule has not fired yet, it reads **No executions yet** with a note that the first instance appears after the next scheduled fire. 3. Once instances exist, review them to see how each run went, and drill into individual runs for their contact-level outcomes. ### 3. Act on the schedule Move from reviewing to managing the schedule. 1. Select **Edit** to change the cadence, recipients, or content — see [Edit recurring schedule](/docs/edit-recurring-schedule). 2. Select **Pause** to stop the schedule temporarily (resume it later), or **Cancel** to stop it permanently. 3. Cancelling asks for confirmation and warns that **no future instances will be created**, though existing instances are not affected. ## Tips and troubleshooting - Use recurring schedules for repeating operational sends, not one-off campaigns. - Review upcoming instances after editing a recurring schedule so you know which future sends changed. - Next Fire and Last Run tell you at a glance whether the schedule is producing runs on its cadence. - Pause a schedule to stop it temporarily; cancelling is permanent and creates no future instances. ## Related pages - [Schedules](https://docs.magickvoice.com/docs/schedules) - [Schedule detail](https://docs.magickvoice.com/docs/schedule-detail) - [Recurring schedules](https://docs.magickvoice.com/docs/recurring-schedules) - [New recurring schedule](https://docs.magickvoice.com/docs/new-recurring-schedule) --- # Contact lists > Manage imported recipient lists used by campaigns, calls, schedules, and messaging workflows. - **Section:** Contacts - **Audience:** Campaign and data managers - **Page address:** `/app/contact-lists` ## Common tasks - Upload a contact list - Search lists - Open list details - Validate list readiness ## How to use this page ### 1. Use this page to manage contacts, catalogs, and documents Understand what is available on Contact lists and choose the right next action. 1. Open Contact lists from the Contacts area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use detail pages to validate imported rows, files, and test queries before using data in live workflows. - Keep names descriptive because lists and documents appear in campaign, automation, and prompt pickers. ## Related pages - [Contact list detail](https://docs.magickvoice.com/docs/contact-list-detail) - [Catalogs](https://docs.magickvoice.com/docs/catalogs) - [Catalog detail](https://docs.magickvoice.com/docs/catalog-detail) - [Documents](https://docs.magickvoice.com/docs/documents) --- # Contact list detail > Inspect contacts, columns, import status, and row-level details for a recipient list. - **Section:** Contacts - **Audience:** Campaign and data managers - **Page address:** `/app/contact-lists/:id` ## Common tasks - Review list summary - Check imported rows - Find invalid records - Use the list in a campaign ## How to use this page ### 1. Use this page to manage contacts, catalogs, and documents Understand what is available on Contact list detail and choose the right next action. 1. Open Contact list detail from the Contacts area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use detail pages to validate imported rows, files, and test queries before using data in live workflows. - Keep names descriptive because lists and documents appear in campaign, automation, and prompt pickers. ## Related pages - [Contact lists](https://docs.magickvoice.com/docs/contact-lists) - [Catalogs](https://docs.magickvoice.com/docs/catalogs) - [Catalog detail](https://docs.magickvoice.com/docs/catalog-detail) - [Documents](https://docs.magickvoice.com/docs/documents) --- # Catalogs > Manage product or service catalogs that call scripts and automations can reference. - **Section:** Contacts - **Audience:** Knowledge managers - **Page address:** `/app/catalogs` - **Access:** Your admin may need to enable this feature ## Common tasks - Create a catalog - Search catalogs - Open catalog details - Prepare catalog data for prompts ## How to use this page ### 1. Use this page to manage contacts, catalogs, and documents Understand what is available on Catalogs and choose the right next action. 1. Open Catalogs from the Contacts area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use detail pages to validate imported rows, files, and test queries before using data in live workflows. - Keep names descriptive because lists and documents appear in campaign, automation, and prompt pickers. ## Related pages - [Contact lists](https://docs.magickvoice.com/docs/contact-lists) - [Contact list detail](https://docs.magickvoice.com/docs/contact-list-detail) - [Catalog detail](https://docs.magickvoice.com/docs/catalog-detail) - [Documents](https://docs.magickvoice.com/docs/documents) --- # Catalog detail > Review catalog entries, test lookup behavior, and confirm catalog readiness for AI workflows. - **Section:** Contacts - **Audience:** Knowledge managers - **Page address:** `/app/catalogs/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Inspect catalog entries - Run a test lookup - Fix missing fields - Use catalog in a script ## How to use this page ### 1. Use this page to manage contacts, catalogs, and documents Understand what is available on Catalog detail and choose the right next action. 1. Open Catalog detail from the Contacts area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use detail pages to validate imported rows, files, and test queries before using data in live workflows. - Keep names descriptive because lists and documents appear in campaign, automation, and prompt pickers. ## Related pages - [Contact lists](https://docs.magickvoice.com/docs/contact-lists) - [Contact list detail](https://docs.magickvoice.com/docs/contact-list-detail) - [Catalogs](https://docs.magickvoice.com/docs/catalogs) - [Documents](https://docs.magickvoice.com/docs/documents) --- # Documents > Manage knowledge documents that can be attached to prompts and used to answer caller questions. - **Section:** Contacts - **Audience:** Knowledge managers - **Page address:** `/app/documents` - **Access:** Your admin may need to enable this feature ## Common tasks - Upload a document - Search documents - Open document detail - Check processing state ## How to use this page ### 1. Use this page to manage contacts, catalogs, and documents Understand what is available on Documents and choose the right next action. 1. Open Documents from the Contacts area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use detail pages to validate imported rows, files, and test queries before using data in live workflows. - Keep names descriptive because lists and documents appear in campaign, automation, and prompt pickers. ## Related pages - [Contact lists](https://docs.magickvoice.com/docs/contact-lists) - [Contact list detail](https://docs.magickvoice.com/docs/contact-list-detail) - [Catalogs](https://docs.magickvoice.com/docs/catalogs) - [Catalog detail](https://docs.magickvoice.com/docs/catalog-detail) --- # Document detail > Inspect a knowledge document, its files, chunks, metadata, and test answers against the uploaded content. - **Section:** Contacts - **Audience:** Knowledge managers - **Page address:** `/app/documents/:id` - **Access:** Your admin may need to enable this feature ## Common tasks - Review uploaded files - Test document answers - Inspect chunks - Upload an updated file ## How to use this page ### 1. Use this page to manage contacts, catalogs, and documents Understand what is available on Document detail and choose the right next action. 1. Open Document detail from the Contacts area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use detail pages to validate imported rows, files, and test queries before using data in live workflows. - Keep names descriptive because lists and documents appear in campaign, automation, and prompt pickers. ## Related pages - [Contact lists](https://docs.magickvoice.com/docs/contact-lists) - [Contact list detail](https://docs.magickvoice.com/docs/contact-list-detail) - [Catalogs](https://docs.magickvoice.com/docs/catalogs) - [Catalog detail](https://docs.magickvoice.com/docs/catalog-detail) --- # Document file detail > Review a specific file inside a knowledge document and inspect its processing or extraction output. - **Section:** Contacts - **Audience:** Knowledge managers - **Page address:** `/app/documents/:id/files/:docId` - **Access:** Your admin may need to enable this feature ## Common tasks - Open file metadata - Inspect extracted content - Troubleshoot processing issues ## How to use this page ### 1. Use this page to manage contacts, catalogs, and documents Understand what is available on Document file detail and choose the right next action. 1. Open Document file detail from the Contacts area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use detail pages to validate imported rows, files, and test queries before using data in live workflows. - Keep names descriptive because lists and documents appear in campaign, automation, and prompt pickers. ## Related pages - [Contact lists](https://docs.magickvoice.com/docs/contact-lists) - [Contact list detail](https://docs.magickvoice.com/docs/contact-list-detail) - [Catalogs](https://docs.magickvoice.com/docs/catalogs) - [Catalog detail](https://docs.magickvoice.com/docs/catalog-detail) --- # Team > Invite teammates, manage roles, and review team membership. - **Section:** Administration - **Audience:** Workspace admins - **Page address:** `/app/team` ## Common tasks - Invite a user - Change a role - Remove access - Confirm team analytics ## How to use this page ### 1. Use this page to manage workspace settings Understand what is available on Team and choose the right next action. 1. Open Team from the Administration area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use the audit log after configuration changes to confirm who changed what and when. - Rotate API keys and remove unused phone numbers as part of regular workspace hygiene. ## Related pages - [Accounts](https://docs.magickvoice.com/docs/accounts) - [Credits](https://docs.magickvoice.com/docs/credits) - [API keys](https://docs.magickvoice.com/docs/api-keys) - [Audit log](https://docs.magickvoice.com/docs/audit-log) --- # Accounts > Manage account records and billing-related account organization used by the workspace. - **Section:** Administration - **Audience:** Workspace admins - **Page address:** `/app/accounts` ## Common tasks - Review accounts - Create an account - Open account details - Confirm ownership ## How to use this page ### 1. Use this page to manage workspace settings Understand what is available on Accounts and choose the right next action. 1. Open Accounts from the Administration area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use the audit log after configuration changes to confirm who changed what and when. - Rotate API keys and remove unused phone numbers as part of regular workspace hygiene. ## Related pages - [Team](https://docs.magickvoice.com/docs/team) - [Credits](https://docs.magickvoice.com/docs/credits) - [API keys](https://docs.magickvoice.com/docs/api-keys) - [Audit log](https://docs.magickvoice.com/docs/audit-log) --- # Credits > Review credit balance, consumption, pricing, and recharge readiness. - **Section:** Administration - **Audience:** Workspace admins and finance users - **Page address:** `/app/credits` ## Common tasks - Check available credits - Review usage - Estimate upcoming spend - Plan recharge timing ## How to use this page ### 1. Use this page to manage workspace settings Understand what is available on Credits and choose the right next action. 1. Open Credits from the Administration area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use the audit log after configuration changes to confirm who changed what and when. - Rotate API keys and remove unused phone numbers as part of regular workspace hygiene. ## Related pages - [Team](https://docs.magickvoice.com/docs/team) - [Accounts](https://docs.magickvoice.com/docs/accounts) - [API keys](https://docs.magickvoice.com/docs/api-keys) - [Audit log](https://docs.magickvoice.com/docs/audit-log) --- # API keys > Create and manage API keys used by external systems to access MagickVoice APIs. - **Section:** Administration - **Audience:** Developers and admins - **Page address:** `/app/api-keys` ## Common tasks - Create an API key - Copy a new key once - Rotate a key - Delete unused keys ## How to use this page ### 1. Use this page to manage workspace settings Understand what is available on API keys and choose the right next action. 1. Open API keys from the Administration area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use the audit log after configuration changes to confirm who changed what and when. - Rotate API keys and remove unused phone numbers as part of regular workspace hygiene. ## Related pages - [Team](https://docs.magickvoice.com/docs/team) - [Accounts](https://docs.magickvoice.com/docs/accounts) - [Credits](https://docs.magickvoice.com/docs/credits) - [Audit log](https://docs.magickvoice.com/docs/audit-log) --- # Audit log > Search workspace audit events to understand who changed what and when. - **Section:** Administration - **Audience:** Workspace admins and compliance users - **Page address:** `/app/audit-log` ## Common tasks - Filter by actor or event - Review event details - Investigate configuration changes - Export evidence where needed ## How to use this page ### 1. Use this page to manage workspace settings Understand what is available on Audit log and choose the right next action. 1. Open Audit log from the Administration area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use the audit log after configuration changes to confirm who changed what and when. - Rotate API keys and remove unused phone numbers as part of regular workspace hygiene. ## Related pages - [Team](https://docs.magickvoice.com/docs/team) - [Accounts](https://docs.magickvoice.com/docs/accounts) - [Credits](https://docs.magickvoice.com/docs/credits) - [API keys](https://docs.magickvoice.com/docs/api-keys) --- # Settings > Manage tenant-level settings and workspace configuration. - **Section:** Administration - **Audience:** Workspace admins - **Page address:** `/app/settings` ## Common tasks - Review workspace settings - Update tenant details - Save configuration changes - Verify changes in audit log ## How to use this page ### 1. Use this page to manage workspace settings Understand what is available on Settings and choose the right next action. 1. Open Settings from the Administration area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use the audit log after configuration changes to confirm who changed what and when. - Rotate API keys and remove unused phone numbers as part of regular workspace hygiene. ## Related pages - [Team](https://docs.magickvoice.com/docs/team) - [Accounts](https://docs.magickvoice.com/docs/accounts) - [Credits](https://docs.magickvoice.com/docs/credits) - [API keys](https://docs.magickvoice.com/docs/api-keys) --- # Phone numbers > Manage phone numbers available for calls, campaigns, and sender selection. - **Section:** Administration - **Audience:** Telephony admins - **Page address:** `/app/phone-numbers` ## Common tasks - Review available numbers - Assign or release numbers - Check number readiness - Use numbers in campaigns ## How to use this page ### 1. Use this page to manage workspace settings Understand what is available on Phone numbers and choose the right next action. 1. Open Phone numbers from the Administration area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use the audit log after configuration changes to confirm who changed what and when. - Rotate API keys and remove unused phone numbers as part of regular workspace hygiene. ## Related pages - [Team](https://docs.magickvoice.com/docs/team) - [Accounts](https://docs.magickvoice.com/docs/accounts) - [Credits](https://docs.magickvoice.com/docs/credits) - [API keys](https://docs.magickvoice.com/docs/api-keys) --- # Super admin home > Open the default super-admin tenant operations view for platform-level customer management. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin` ## Common tasks - Search tenants - Open tenant detail - Review tenant health - Navigate platform tools ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin home and choose the right next action. 1. Open Super admin home from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) - [Super admin admins](https://docs.magickvoice.com/docs/super-admin-admins) --- # Super admin tenants > Review and manage tenants from the explicit tenant route. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/tenants` ## Common tasks - Search tenants - Open tenant detail - Compare tenant state - Investigate customer issues ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin tenants and choose the right next action. 1. Open Super admin tenants from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) - [Super admin admins](https://docs.magickvoice.com/docs/super-admin-admins) --- # Super admin tenant detail > Inspect a tenant, its usage, feature flags, governance, users, and operational state. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/tenants/:id` ## Common tasks - Review tenant profile - Inspect feature access - Check usage or credits - Investigate tenant-specific issues ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin tenant detail and choose the right next action. 1. Open Super admin tenant detail from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) - [Super admin admins](https://docs.magickvoice.com/docs/super-admin-admins) --- # Super admin users > Search platform users and investigate account-level access questions. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/users` ## Common tasks - Search users - Review user identity - Find tenant membership - Investigate access problems ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin users and choose the right next action. 1. Open Super admin users from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin admins](https://docs.magickvoice.com/docs/super-admin-admins) --- # Super admin admins > Manage the set of users with super-admin permissions. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/admins` ## Common tasks - Review admin list - Add an admin when approved - Remove admin access - Confirm changes in audit logs ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin admins and choose the right next action. 1. Open Super admin admins from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) --- # Super admin providers > Inspect provider configuration and platform-level integrations. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/providers` ## Common tasks - Review providers - Check provider health - Inspect configuration - Investigate provider issues ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin providers and choose the right next action. 1. Open Super admin providers from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) --- # Super admin phone numbers > Manage phone numbers at platform scope across tenants. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/phone-numbers` ## Common tasks - Search numbers - Review tenant assignment - Investigate availability - Resolve number conflicts ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin phone numbers and choose the right next action. 1. Open Super admin phone numbers from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) --- # Super admin feature flags > Control feature flag rollout and tenant-specific feature access. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/feature-flags` ## Common tasks - Search flags - Review rollout state - Apply tenant override - Verify flag behavior ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin feature flags and choose the right next action. 1. Open Super admin feature flags from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) --- # Super admin governance > Manage governance capabilities and entitlement controls that determine what tenants can use. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/governance` ## Common tasks - Review capabilities - Adjust tenant access - Confirm dependencies - Audit governance changes ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin governance and choose the right next action. 1. Open Super admin governance from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) --- # Super admin usage > Analyze platform usage across tenants for operational and billing insight. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/usage` ## Common tasks - Set usage period - Compare tenant usage - Identify anomalies - Open tenant detail for follow-up ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin usage and choose the right next action. 1. Open Super admin usage from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users) --- # Super admin audit > Search platform-level audit events for investigation, compliance, and support escalation. - **Section:** Super Admin - **Audience:** Super admins - **Page address:** `/super-admin/audit` ## Common tasks - Filter audit events - Review event payloads - Trace actor activity - Export or record evidence ## How to use this page ### 1. Use this page to operate the platform as a super admin Understand what is available on Super admin audit and choose the right next action. 1. Open Super admin audit from the Super Admin area of MagickVoice. 2. Read the page heading, description, and any status message before selecting an action. 3. Choose the common task that matches what you came to do and follow the labels shown on screen. 4. Review any summary, warning, or confirmation before completing an action that changes data. 5. After the action finishes, look for a confirmation message or updated status before leaving the page. ## Tips and troubleshooting - Use tenant detail and audit pages together when investigating a customer-impacting change. - Prefer scoped changes over broad platform toggles unless the rollout plan explicitly calls for a global change. ## Related pages - [Super admin home](https://docs.magickvoice.com/docs/super-admin-home) - [Super admin tenants](https://docs.magickvoice.com/docs/super-admin-tenants) - [Super admin tenant detail](https://docs.magickvoice.com/docs/super-admin-tenant-detail) - [Super admin users](https://docs.magickvoice.com/docs/super-admin-users)