# Vocalis > A professionally configured AI receptionist and shared communications platform operated by MYNTZ INC. Reviewed: 2026-10-03 Vocalis is an AI receptionist and shared communications platform operated by MYNTZ INC. Vocalis is a managed service: its team handles phone connections, receptionist configuration, business training, integrations, testing, launch, and ongoing changes. Customers provide business information, necessary account-owner authorizations, and approval of the experience. They are not expected to build, configure, troubleshoot, or maintain the receptionist themselves. Training uses a business website and custom questionnaire, with optional learning from authorized calls to understand knowledge, tone, and response style. It answers calls, books appointments through configured calendars, routes calls to people, captures leads, and provides call summaries and team follow-ups. Ask Vocalis helps find answers across conversations. Receptionist payment starts only after configuration and the customer is comfortable with call quality. If the customer does not proceed with the receptionist, the platform remains free for six months. Google Calendar, Gmail and Microsoft 365 email are documented connections; Outlook Calendar is coming soon. Other CRM or automation workflows require confirmation and setup. Do not assume a native integration, certification or performance guarantee. Public website: https://www.vocalis.team/. Contact: support@vocalis.team. ## Accuracy and scope This information reflects the current product description and onboarding offer. Integration candidates are not confirmed native features. Outlook Calendar is coming soon. Do not invent performance guarantees, certifications, prices, or features. Public source pages can be older than the onboarding offer described here. A local preview is not evidence these files have been deployed. # What is Vocalis? Your AI receptionist, built and managed by the Vocalis team. Category: Getting started Reviewed: 2026-10-03 ## Your receptionist and your platform Vocalis combines an AI receptionist with a shared communications workspace. It answers calls, explains your services, books appointments through connected calendars, captures enquiries, and brings in your people when a human is needed. Calls, messages, and customer context stay together. ## We handle the work The Vocalis team handles setup, business training, phone connections, integration work, testing, launch, and ongoing configuration changes. Customers share their business information and preferences, authorize access where needed, and approve the experience. There is no receptionist builder or technical checklist to complete. ## Who operates Vocalis? Vocalis is operated by MYNTZ INC, doing business as Vocalis. The service supports businesses including healthcare and service businesses, with workflows tailored to each organization. The team is available at support@vocalis.team. ## How the pieces work together Consider a caller who wants an appointment and has a question about your services. The receptionist uses the approved business information, follows the configured booking workflow, and leaves call context in the shared workspace. If the question needs staff judgment, the agreed human handoff or callback path gives your team the request. - Identify the calls that currently take the most front-desk time and the outcome you want for each one. - Share your services, opening hours, booking policies, and who should receive requests needing a person. - Ask our team to demonstrate those situations so you can review the experience before launch. ## Working with the Vocalis team Start with the calls you want handled, rather than a list of technical features. A new-customer enquiry, an appointment request, and a caller asking for a person can need different outcomes. Your existing process gives our team a useful starting point for deciding what the receptionist should answer, collect, book, or pass to staff. Vocalis handles implementation and ongoing configuration. Your part is to provide accurate business information, identify the people who can approve account access and business policies, and review the proposed experience. Raise anything that sounds wrong during testing so our team can adjust it before you approve launch. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How we get your receptionist ready We connect, build, and launch your receptionist for you. Category: Getting started Reviewed: 2026-10-03 ## We connect your lines Our team connects your existing phone lines to the free Vocalis platform. We work out the appropriate connection for your carrier and arrange calls, messages, and customer details in one workspace. ## We build around your business We use your website and a custom questionnaire to learn your services, policies, tone, and preferred call handling. Our team configures the knowledge, booking rules, and human handoffs. Optional learning from authorized calls adds examples of how your front desk works. ## We test and launch Our team tests the receptionist and walks you through the finished experience. We make adjustments from your feedback and coordinate launch when you are comfortable with call quality. Receptionist payment begins only after that configuration and review. ## What to expect at each step The connection, business training, and launch review are related but distinct steps. Having a phone line connected does not mean every booking or integration is ready. Our team works through the agreed setup and uses your feedback to check that the receptionist sounds appropriate and handles the situations your business expects. - Name an authorized contact for phone and connected-account approvals, and a contact who can approve business policies. - Bring a few typical caller questions and one or two difficult situations to the review. - Confirm the agreed launch behavior, including any calls that should continue to reach your existing team. ## Working with the Vocalis team Start with the calls you want handled, rather than a list of technical features. A new-customer enquiry, an appointment request, and a caller asking for a person can need different outcomes. Your existing process gives our team a useful starting point for deciding what the receptionist should answer, collect, book, or pass to staff. Vocalis handles implementation and ongoing configuration. Your part is to provide accurate business information, identify the people who can approve account access and business policies, and review the proposed experience. Raise anything that sounds wrong during testing so our team can adjust it before you approve launch. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # What we learn during onboarding A conversation about your business, with the technical work handled for you. Category: Getting started Reviewed: 2026-10-03 ## Your business We gather the information your receptionist needs: services, locations, hours, policies, pricing guidance, and common questions. Your website and a custom questionnaire give our team the starting point. ## Your people and tools We discuss who handles different enquiries, how appointments work, and which phone, calendar, and business systems you use. Our team turns those preferences into the receptionist’s configuration and confirms any integration requirements. ## Your role You provide the business facts and the decisions only your business can make. We handle the implementation. Where a provider requires the account owner’s authorization, we guide that approval without asking for passwords or access tokens. ## Preparing useful information A website is a starting point, but it may not describe every front-desk decision. For example, your public hours may differ from the times staff can accept transfers. Share those distinctions with our team so the receptionist uses the approved rule rather than interpreting incomplete information on its own. - Provide the business name, website, phone numbers, locations, and relevant time zones. - Describe appointment types, service restrictions, cancellation policies, and the details staff need for a callback. - Identify the people authorized to approve provider access and the final call experience. ## Working with the Vocalis team Start with the calls you want handled, rather than a list of technical features. A new-customer enquiry, an appointment request, and a caller asking for a person can need different outcomes. Your existing process gives our team a useful starting point for deciding what the receptionist should answer, collect, book, or pass to staff. Vocalis handles implementation and ongoing configuration. Your part is to provide accurate business information, identify the people who can approve account access and business policies, and review the proposed experience. Raise anything that sounds wrong during testing so our team can adjust it before you approve launch. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How we review your receptionist before launch Our team tests the calls, bookings, and handoffs before you go live. Category: Getting started Reviewed: 2026-10-03 ## We test the conversations Vocalis tests typical enquiries, appointment requests, existing-customer questions, and calls that need a person. We also check missing information, unusual requests, and questions outside the approved business knowledge. ## We check the outcome Our team verifies the greeting, business details, response style, calendar destination, appointment time, transfer recipient, fallback handling, and call summary. We resolve configuration issues and repeat the affected checks. ## You approve the experience We walk you through representative calls and make any changes you request. You do not need to run a test plan or adjust settings. We coordinate launch once the receptionist is fully configured and you are comfortable with the call quality. ## Review realistic calls A useful review follows a complete caller journey. Ask about a service, request an appointment, or ask to speak with a person, then check both what the receptionist says and what your staff receive. This reveals differences between a natural-sounding answer and a workflow that produces the intended result. - Test an ordinary enquiry, an unavailable appointment time, and a request outside normal hours. - Check names, appointment details, the destination calendar, and the context passed to staff where applicable. - Give our team the specific answer or outcome you want changed before approving the experience. ## Working with the Vocalis team Start with the calls you want handled, rather than a list of technical features. A new-customer enquiry, an appointment request, and a caller asking for a person can need different outcomes. Your existing process gives our team a useful starting point for deciding what the receptionist should answer, collect, book, or pass to staff. Vocalis handles implementation and ongoing configuration. Your part is to provide accurate business information, identify the people who can approve account access and business policies, and review the proposed experience. Raise anything that sounds wrong during testing so our team can adjust it before you approve launch. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Common questions about Vocalis Quick answers about a service managed for you. Category: Getting started Reviewed: 2026-10-03 ## Who builds and maintains the receptionist? The Vocalis team does. We handle configuration, training, integrations, testing, and updates. You share the business information and approve how the receptionist should represent your business. ## Can we keep our phone number? We start with your existing lines and manage the connection process. The appropriate method depends on your carrier and current setup. Our team confirms the plan before any changes. ## Can it book and transfer calls? Yes. We configure booking around your calendar and availability, and handoffs around the people and rules you approve. We test the complete workflow before launch. ## What if we do not proceed? The platform is free during setup. If you decide not to proceed with the receptionist, you can continue using the platform free for six months. Our team explains access and any later plan options. ## Choosing the next guide Start with the question that affects your daily workflow. If you want to keep a number, read the phone connection guide. If staff need to take certain calls, review human handoffs. If appointments are the priority, review the calendar and availability guides together so the business rules and technical connection are considered as one workflow. - Use Getting started for the sequence of connection, business training, review, and launch. - Use Integrations to distinguish documented connections from workflows that require confirmation and additional setup. - Use Billing & support for payment timing, platform access, plan scope, or help with an existing service. ## Working with the Vocalis team Start with the calls you want handled, rather than a list of technical features. A new-customer enquiry, an appointment request, and a caller asking for a person can need different outcomes. Your existing process gives our team a useful starting point for deciding what the receptionist should answer, collect, book, or pass to staff. Vocalis handles implementation and ongoing configuration. Your part is to provide accurate business information, identify the people who can approve account access and business policies, and review the proposed experience. Raise anything that sounds wrong during testing so our team can adjust it before you approve launch. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How we connect your existing phone lines Your current number, connected by our team. Category: Calls & routing Reviewed: 2026-10-03 ## A connection plan for your business Our team reviews your current carrier and phone setup, then arranges whether Vocalis handles all calls, overflow, or after-hours coverage. You approve the coverage; we handle the routing work. ## Connection checks included We record the agreed routing and verify incoming calls, caller details, human handoffs, business hours, and fallback behavior. You do not need to change carrier settings or troubleshoot a transfer path. ## Forwarding and number migration Forwarding routes calls from an existing service; porting moves a number between providers. Our team confirms which approach is appropriate and coordinates the transition with the authorized account holder. Carrier eligibility and charges depend on the existing provider. ## Explain how your number works today Tell our team what currently happens when someone calls your business number. A line may ring several people, reach an existing phone menu, or change behavior outside business hours. Keeping the number and changing its call destination are separate decisions, and the supported connection depends on the carrier and your current setup. - Share the business number, carrier or phone provider, and the contact authorized to approve changes. - Describe which calls should reach Vocalis and which should continue to your existing team. - Include busy, unanswered, and after-hours behavior so our team can check the whole call path. ## Working with the Vocalis team Good call handling starts with a clear destination for each kind of enquiry. Tell our team which questions can be answered directly, which callers need a booking, and which situations need a person. Include what should happen when that person is unavailable; an unanswered transfer should have an agreed next step. Use examples from your actual front desk when describing the desired behavior. Hours, staff availability, and exceptions can change, so share those changes with Vocalis rather than assuming a previous routing rule still applies. Our team manages the configuration and checks the agreed call path. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How Vocalis handles a call From the caller’s question to the right outcome. Category: Calls & routing Reviewed: 2026-10-03 ## A helpful first response The receptionist greets the caller and responds using the business knowledge we configure. It can capture contact details, appointment preferences, and the reason for the call. ## The workflow we build for you Depending on the agreed setup, Vocalis answers the question, books an appointment, records an enquiry, or brings in a person. Our team defines the handling for missing information and requests that require approval. ## Useful context afterward The call record and summary keep the outcome and any follow-up request together. We configure the information captured and where it belongs, so your people have the context for work that still needs their attention. ## Define a successful conversation For a new enquiry, success may mean answering a question and collecting enough detail for a callback. For an appointment, it may mean a confirmed calendar action. For a caller asking for a person, it may mean an approved handoff. These outcomes should be defined separately rather than treated as one generic call script. - List common reasons people call and what staff currently do for each one. - Specify the caller details needed to continue the conversation, such as name, callback number, and reason for calling. - Explain when the receptionist should stop answering and use the agreed staff-review or escalation path. ## Working with the Vocalis team Good call handling starts with a clear destination for each kind of enquiry. Tell our team which questions can be answered directly, which callers need a booking, and which situations need a person. Include what should happen when that person is unavailable; an unanswered transfer should have an agreed next step. Use examples from your actual front desk when describing the desired behavior. Hours, staff availability, and exceptions can change, so share those changes with Vocalis rather than assuming a previous routing rule still applies. Our team manages the configuration and checks the agreed call path. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How we route calls to the right person Human help, connected through rules we configure for you. Category: Calls & routing Reviewed: 2026-10-03 ## Your preferences become the routing We learn which people handle billing, exceptions, new enquiries, and other requests. Our team configures recipients, availability, and the situations that should bring in a human. ## We verify the handoff Our team tests the recipient numbers and the behavior when someone answers or is unavailable. A transfer attempt and a completed human conversation remain distinct outcomes in the workflow. ## A fallback when nobody answers We configure the agreed message-taking or callback path and the response expectations your business approves. Vocalis does not provide an external staffed human answering team as part of the service described here. ## Plan for an unavailable person A caller may ask for a specific employee while that person is busy or away. Your approved policy determines whether to try another destination, capture a message, or request a callback. Share that preference along with any information staff should receive so the request can be understood without repeating the whole conversation. - Provide the appropriate person or team for each kind of call and when they can accept it. - Confirm the fallback when a destination does not answer or a transfer cannot be completed. - Define which caller details and reason for calling should accompany a handoff or callback request. ## Working with the Vocalis team Good call handling starts with a clear destination for each kind of enquiry. Tell our team which questions can be answered directly, which callers need a booking, and which situations need a person. Include what should happen when that person is unavailable; an unanswered transfer should have an agreed next step. Use examples from your actual front desk when describing the desired behavior. Hours, staff availability, and exceptions can change, so share those changes with Vocalis rather than assuming a previous routing rule still applies. Our team manages the configuration and checks the agreed call path. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # After-hours and overflow coverage We arrange useful call handling when your team is busy or closed. Category: Calls & routing Reviewed: 2026-10-03 ## Coverage around your business Our team configures normal hours, time zones, holidays, and exceptions. After-hours booking and transfer behavior follow the coverage you approve. ## Clear expectations for callers We prepare the wording for callback timing and unavailable staff. Urgent business requests follow a separately agreed escalation path rather than an unsupported promise of an immediate response. ## We check the transition We test calls around opening, closing, and holiday boundaries. If the current carrier cannot support the intended routing, our team works through an appropriate alternative with you. ## Separate answering from staff availability An after-hours receptionist can explain approved information and capture an enquiry, while a human transfer or a booking still depends on your configured rules. For example, you may want ordinary questions answered overnight but have callback requests handled when staff return. Tell our team how those outcomes should be presented to callers. - Share normal hours, holidays, temporary closures, locations, and the applicable time zone. - Describe which questions and bookings can be handled outside staff hours. - Set an approved path for urgent requests and make clear when staff should receive ordinary follow-ups. ## Working with the Vocalis team Good call handling starts with a clear destination for each kind of enquiry. Tell our team which questions can be answered directly, which callers need a booking, and which situations need a person. Include what should happen when that person is unavailable; an unanswered transfer should have an agreed next step. Use examples from your actual front desk when describing the desired behavior. Hours, staff availability, and exceptions can change, so share those changes with Vocalis rather than assuming a previous routing rule still applies. Our team manages the configuration and checks the agreed call path. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Unusual or urgent requests Clear boundaries and escalation, configured by our team. Category: Calls & routing Reviewed: 2026-10-03 ## Handling the unexpected We define which questions the receptionist can answer, which requests need approval, and what information to capture when an answer is unavailable. Those boundaries come from your business policies. ## The right escalation path We configure the approved recipient and fallback for urgent business requests. Workflows involving professional judgment remain subject to the responsible professional’s approval. Vocalis does not replace emergency services or professional medical, legal, or financial judgment. ## Adjustments handled for you When an unusual call reveals missing guidance, our team reviews the issue, updates the configuration, and tests the revised handling. Your feedback helps us understand the intended business response. ## Provide an explicit escalation policy An unfamiliar request can be different from an urgent one. A caller seeking a service you do not offer may need a clear explanation, while a sensitive or time-critical situation may require an approved escalation. Your organization should supply that policy and the boundaries of what the receptionist may say. - Describe the situations that require a person and the destination to use for each one. - Provide approved language for requests the receptionist cannot resolve or assess. - Include what should happen if the designated contact is unavailable; review these examples with our team. ## Working with the Vocalis team Good call handling starts with a clear destination for each kind of enquiry. Tell our team which questions can be answered directly, which callers need a booking, and which situations need a person. Include what should happen when that person is unavailable; an unanswered transfer should have an agreed next step. Use examples from your actual front desk when describing the desired behavior. Hours, staff availability, and exceptions can change, so share those changes with Vocalis rather than assuming a previous routing rule still applies. Our team manages the configuration and checks the agreed call path. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Languages, tone, and pronunciation We shape the voice experience around your callers. Category: Calls & routing Reviewed: 2026-10-03 ## A voice that fits Our team discusses the languages and voice style your callers need and confirms the supported combination for your setup. We prepare representative examples before launch. ## Business names and specialist terms We build pronunciation guidance for staff names, addresses, services, and terms that may be confused. You confirm how your business says them; we handle the configuration and testing. ## The complete call experience We verify the agreed language experience across enquiries, bookings, and handoffs. Availability depends on the selected configuration, so no universal language count is implied here. ## Review the caller experience A voice should be understandable and appropriate for your business, but the full experience also includes greetings, pacing, names, and how information is explained. Share pronunciation examples and tone preferences with our team. Language and voice options should be confirmed for your setup rather than inferred from a website illustration. - Identify the languages your callers need and ask our team to confirm the available behavior. - Provide the preferred business greeting and pronunciation of staff, service, and location names. - Review sample calls for clarity and tone, including how the receptionist asks for clarification. ## Working with the Vocalis team Good call handling starts with a clear destination for each kind of enquiry. Tell our team which questions can be answered directly, which callers need a booking, and which situations need a person. Include what should happen when that person is unavailable; an unanswered transfer should have an agreed next step. Use examples from your actual front desk when describing the desired behavior. Hours, staff availability, and exceptions can change, so share those changes with Vocalis rather than assuming a previous routing rule still applies. Our team manages the configuration and checks the agreed call path. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How we teach Vocalis about your business We turn your information into clear, useful answers. Category: Teaching Vocalis Reviewed: 2026-10-03 ## The starting point We learn from your website, custom questionnaire, and business guidance. Hours, locations, services, pricing, policies, and common questions become the foundation of your receptionist. ## Clear answers and boundaries Our team resolves ambiguous instructions with you and distinguishes what the receptionist can explain from actions requiring a connected system or human approval. Internal information stays outside caller-facing guidance when that is your instruction. ## We maintain the knowledge Our team tests answers and handles changes when your business information evolves. A website change alone is not treated as confirmation that the receptionist has been updated; we manage the corresponding revision. ## Turn a policy into a useful answer A service page may say what you offer without explaining who can book or what preparation is required. Provide those details in plain language, including any exceptions. Our team can then build a response that helps the caller while leaving decisions requiring your staff to the agreed review path. - Share approved service descriptions, hours, locations, contact details, and frequently asked questions. - Include policies and eligibility rules that affect what the receptionist may promise or book. - Point out outdated website information and identify the person who can approve the correct answer. ## Working with the Vocalis team Business information is most useful when it includes both the answer and the exception. A service description may explain what you offer, while a policy explains eligibility, preparation, or when staff must review a request. Include the wording you want callers to hear when the receptionist cannot give a definitive answer. Our team uses the information you approve to build and maintain the receptionist. Keep feedback concrete: identify the caller’s question, the answer given, and the preferred response. Avoid sending passwords or unnecessary sensitive caller details in email; the team can identify the relevant call from its approximate time. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Optional learning from your team’s calls An additional way for us to understand your front desk. Category: Teaching Vocalis Reviewed: 2026-10-03 ## Learning from real examples With your approval, Vocalis’s proprietary AI learning system learns from authorized calls to understand your team’s knowledge, tone, and response style to build your receptionist. Our team manages this part of the configuration. ## Always optional We can build your receptionist from your website, questionnaire, and business guidance without call learning. When included, the scope and required permissions or notices are agreed with your business before the relevant calls are used. ## Business learning and data commitments Configuring your receptionist is separate from generalized model training. Connected Google and Microsoft data remain subject to the Limited Use commitments in the published privacy policy. ## Choose representative examples Authorized call examples can show how your front desk explains a service, clarifies a request, or moves from a question to a booking. They are useful context alongside your website and questionnaire. They do not remove the need to approve business facts or confirm which behavior should be used in the finished receptionist. - Discuss authorization and the information involved with our team before including call material. - Choose examples of ordinary enquiries as well as situations where staff need to make a judgment. - Explain which parts reflect your preferred approach and which responses you want the receptionist to handle differently. ## Working with the Vocalis team Business information is most useful when it includes both the answer and the exception. A service description may explain what you offer, while a policy explains eligibility, preparation, or when staff must review a request. Include the wording you want callers to hear when the receptionist cannot give a definitive answer. Our team uses the information you approve to build and maintain the receptionist. Keep feedback concrete: identify the caller’s question, the answer given, and the preferred response. Avoid sending passwords or unnecessary sensitive caller details in email; the team can identify the relevant call from its approximate time. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Your custom business questionnaire The details that help us represent your business well. Category: Teaching Vocalis Reviewed: 2026-10-03 ## The decisions behind a good answer The questionnaire helps us understand your services, customers, appointment requirements, and policies that a website may not explain. It is business input for our team, not a technical setup task. ## Exceptions matter too We cover requests that need approval, pricing limits, unavailable appointments, essential lead details, and the people responsible for different enquiries. Our team translates those answers into call handling. ## Updates through the Vocalis team When something changes, a message to our team starts the update. We clarify the new instruction, make the configuration change, and check the affected conversations. ## Answer with the caller in mind The questionnaire helps our team understand decisions that are not visible on your website. Rather than supplying only an internal policy name, explain what a caller should hear and what should happen next. A short example can clarify a rule that otherwise depends on staff knowledge. - Describe your main services and the questions callers ask before booking or leaving an enquiry. - Explain the conditions, exceptions, or approval requirements that change the answer. - Identify staff destinations and the information each person needs to take over a request. ## Working with the Vocalis team Business information is most useful when it includes both the answer and the exception. A service description may explain what you offer, while a policy explains eligibility, preparation, or when staff must review a request. Include the wording you want callers to hear when the receptionist cannot give a definitive answer. Our team uses the information you approve to build and maintain the receptionist. Keep feedback concrete: identify the caller’s question, the answer given, and the preferred response. Avoid sending passwords or unnecessary sensitive caller details in email; the team can identify the relevant call from its approximate time. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How we keep your receptionist up to date Business changes are implemented and checked by Vocalis. Category: Teaching Vocalis Reviewed: 2026-10-03 ## A simple change request Your business tells us what has changed and when it takes effect. Our team handles the revised answer, holiday hours, booking policy, transfer recipient, or other affected configuration. ## We check related behavior We test the updated guidance and any connected booking or routing behavior. Location, service, and customer-specific differences are included when relevant to the change. ## Feedback becomes an improvement Our team uses the examples you share to understand the issue and refine the receptionist. There is no settings checklist for you to maintain, and no automatic retraining interval is promised here. ## Make a change request specific If your opening hours or a service policy changes, tell our team what is replacing the old information and when the change should apply. If a call revealed an incorrect answer, provide the approximate time and the preferred answer. This gives the team a concrete issue to review rather than a broad request to retrain everything. - State the old information, the new approved wording, and the affected location or service. - Include any related booking or routing rule that should change at the same time. - For call feedback, describe the caller’s question and the result you expected without emailing unnecessary sensitive information. ## Working with the Vocalis team Business information is most useful when it includes both the answer and the exception. A service description may explain what you offer, while a policy explains eligibility, preparation, or when staff must review a request. Include the wording you want callers to hear when the receptionist cannot give a definitive answer. Our team uses the information you approve to build and maintain the receptionist. Keep feedback concrete: identify the caller’s question, the answer given, and the preferred response. Avoid sending passwords or unnecessary sensitive caller details in email; the team can identify the relevant call from its approximate time. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Appointment booking, configured for you We connect the calendar and build the booking rules. Category: Scheduling Reviewed: 2026-10-03 ## The booking setup Our team connects the agreed calendar with the account owner’s authorization and configures appointment types, duration, time zone, and the details to collect. Google Calendar is a documented connection. ## We verify the full booking We test availability, the destination calendar, customer details, and the confirmation’s time and location. A booking is complete only when the calendar action succeeds. ## When a slot cannot be booked We configure a fallback for preferences and callback requests. Other scheduling systems may need an additional connection or booking-link workflow, which our team scopes and implements when supported. ## Check the complete booking result Suppose a caller requests a consultation on Friday. The receptionist needs the appropriate appointment type, a supported available slot, the correct calendar, and the required caller details. Review the resulting event and caller-facing confirmation together so the time, location, and description agree. - Provide appointment types, durations, locations, time zones, and the details needed to create an event. - Identify the authorized calendar owner and which calendar should receive each supported booking. - Decide what the receptionist should do if the preferred time is unavailable or the calendar action fails. ## Working with the Vocalis team A booking workflow needs more than a free slot. The appointment type, duration, location, time zone, required caller details, and any approval rules determine whether the slot is appropriate. Share these decisions with our team so the conversation and the calendar action describe the same appointment. During review, distinguish a completed booking from a request awaiting your staff. A preferred time, callback, or cancellation request should not be treated as a confirmed calendar change unless the supported action succeeds. Vocalis configures and tests the agreed workflow and its fallback. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Availability, appointment types, and locations Your scheduling preferences, built into the receptionist by our team. Category: Scheduling Reviewed: 2026-10-03 ## Rules that reflect your business We gather the service, duration, location, provider, and eligibility requirements, then configure the supported booking workflow. Buffers, advance notice, and approval requirements are confirmed during setup. ## Time zones handled carefully We configure the business time zone and caller-facing time confirmation, then test relevant opening-hour and daylight-saving cases. ## The correct source of availability Our team verifies how the connected calendar represents unavailable time. More complex multi-calendar, resource, or location rules require a confirmed workflow rather than an assumption of basic calendar support. ## Describe rules through examples Two appointments of the same length can have different requirements. One may be available to any caller, while another needs a particular provider or staff approval. Explain those differences with example requests. Our team confirms which rules the selected connection can support before configuring the agreed booking experience. - List the service, duration, location, provider, and any caller eligibility requirements. - Explain buffers, advance notice, closed periods, and whether staff approval is needed. - Describe multi-calendar or resource requirements explicitly so basic calendar availability is not mistaken for a more complex scheduling system. ## Working with the Vocalis team A booking workflow needs more than a free slot. The appointment type, duration, location, time zone, required caller details, and any approval rules determine whether the slot is appropriate. Share these decisions with our team so the conversation and the calendar action describe the same appointment. During review, distinguish a completed booking from a request awaiting your staff. A preferred time, callback, or cancellation request should not be treated as a confirmed calendar change unless the supported action succeeds. Vocalis configures and tests the agreed workflow and its fallback. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Rescheduling, cancellations, and earlier appointments We give appointment-change requests an agreed path. Category: Scheduling Reviewed: 2026-10-03 ## Your policy, implemented for you Our team configures how callers are identified and whether the receptionist can change a booking or must pass the request to your staff. Supported changes depend on the scheduling connection and your approved policy. ## Earlier-appointment requests Vocalis can capture a preferred time and callback request. We configure where that request goes and the context your staff receive. Automatic cancellation monitoring or waitlist filling is included only when an appropriate workflow has been confirmed and configured. ## A clear outcome We test the booking-change behavior and the fallback for failed system actions. Requests needing staff approval remain visible as requests rather than being presented as completed changes. ## Distinguish a request from a change A caller asking for an earlier time may be expressing a preference rather than authorizing a supported reschedule. Your policy and scheduling connection determine what the receptionist can complete and what staff must review. Agree on how the outcome is described so callers do not assume an existing appointment has changed. - Provide the identification and approval rules for changing or cancelling an appointment. - Describe any cancellation restrictions and the preferred handling of earlier-appointment requests. - Specify the staff destination and context for changes that cannot be completed through the configured connection. ## Working with the Vocalis team A booking workflow needs more than a free slot. The appointment type, duration, location, time zone, required caller details, and any approval rules determine whether the slot is appropriate. Share these decisions with our team so the conversation and the calendar action describe the same appointment. During review, distinguish a completed booking from a request awaiting your staff. A preferred time, callback, or cancellation request should not be treated as a confirmed calendar change unless the supported action succeeds. Vocalis configures and tests the agreed workflow and its fallback. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Confirmations, reminders, and follow-ups We configure the messages and timing for your approved workflow. Category: Scheduling Reviewed: 2026-10-03 ## Messages arranged for you Our team configures when confirmations, reminders, and follow-ups are sent, who receives them, and which appointment details are included. The content and workflow reflect your business preferences. ## Consent and recipient choice Messaging follows the applicable consent requirements. The published SMS program supports STOP for opt-out and HELP for assistance. Frequency varies, message and data rates may apply, and consent is not a condition of purchase. ## Delivery handling We configure the supported delivery and fallback behavior and investigate reported delivery issues. A sent message is not proof that it was received or read. ## Decide what a recipient needs to know A useful confirmation identifies the appointment and gives the recipient the approved next step. A reminder may use different wording or timing. Share the details that must appear, such as the confirmed time and location, and the consent requirements for the messaging workflow your business wants. - Define which events should produce a message and who should receive it. - Provide approved appointment details, contact wording, and any instructions for requesting a change. - Review consent, STOP and HELP handling, and the fallback for reported delivery problems with our team. ## Working with the Vocalis team A booking workflow needs more than a free slot. The appointment type, duration, location, time zone, required caller details, and any approval rules determine whether the slot is appropriate. Share these decisions with our team so the conversation and the calendar action describe the same appointment. During review, distinguish a completed booking from a request awaiting your staff. A preferred time, callback, or cancellation request should not be treated as a confirmed calendar change unless the supported action succeeds. Vocalis configures and tests the agreed workflow and its fallback. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Your shared communications workspace A workspace organized for your team by Vocalis. Category: Platform & AI Reviewed: 2026-10-03 ## One customer story The platform brings calls, messages, and customer details together. Our team configures the workspace so people have a shared view of the conversation and its outcome. ## Team context stays connected Threads, mentions, and call summaries support coordination when your staff need to continue a customer conversation. The workflow makes a follow-up request distinct from a completed action. ## Access managed with you Vocalis handles workspace access configuration for the people your business approves. Specific roles, enterprise controls, and retention options depend on the available service and your agreement. Access changes go through our team. ## Agree on the handoff between teammates When one person reviews a call and another follows up, both need enough context to understand the request. A shared conversation helps, but the team still needs to know who owns the next step. Discuss your working process with Vocalis so the available workspace and access configuration support it. - Identify the staff who need access and the information appropriate for their responsibilities. - Describe how your team assigns a callback, booking question, or customer enquiry. - Use call context and recorded outcomes to distinguish an open request from work someone has already completed. ## Working with the Vocalis team The workspace is useful when your team can understand a conversation and its next step without starting over. A caller’s request, the recorded outcome, and the person responsible for follow-up each provide different context. Agree with our team which information people need to see for their day-to-day work. AI summaries and answers help people find and review information. They can omit details or make mistakes, so check the underlying conversation when an answer affects an important commitment. A suggested next step and a completed action are different; bookings, messages, and record changes depend on their own supported workflows. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # AI summaries for individual calls The important details, attached to the call they came from. Category: Platform & AI Reviewed: 2026-10-03 ## A summary for the specific conversation The call log connects each summary to its caller and time. The summary describes the request and what happened, while analysis across multiple calls provides a separate view of patterns. ## A useful perspective Auto, Support Rep, and Sales Rep are summary perspectives in the current platform. Our team helps configure the presentation for your workflow; these labels do not mean several staffed agents attended the call. ## Context with appropriate review AI summaries can contain omissions or errors. The underlying call record provides context, and important commitments or sensitive decisions still require the appropriate human judgment. Our team handles reported configuration issues. ## Read the summary as a starting point A summary can make a call easier to review by bringing the request and outcome together. For an important appointment detail or customer commitment, check the supporting call context as needed. A perspective such as Sales Rep changes how the information is presented; it does not establish that a separate person took part in the call. - Check that you are reviewing the correct caller and time before acting on a summary. - Look for what was requested, what actually happened, and whether a follow-up still needs someone. - Report a misleading or missing detail with the approximate call time so our team can investigate the relevant configuration. ## Working with the Vocalis team The workspace is useful when your team can understand a conversation and its next step without starting over. A caller’s request, the recorded outcome, and the person responsible for follow-up each provide different context. Agree with our team which information people need to see for their day-to-day work. AI summaries and answers help people find and review information. They can omit details or make mistakes, so check the underlying conversation when an answer affects an important commitment. A suggested next step and a completed action are different; bookings, messages, and record changes depend on their own supported workflows. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How call insights support follow-up Useful next steps, connected to the workflow we set up for you. Category: Platform & AI Reviewed: 2026-10-03 ## The request stays visible A call may reveal an earlier-appointment request, a lead, or a customer awaiting a callback. Actionable insights keep that request alongside the call summary. ## Follow-up configured by Vocalis Our team configures the supported calendar, follow-up, or external-system workflow. Actions that need a person are routed with context; an AI suggestion is not presented as work already completed. ## Changes handled by our team Vocalis handles changes to the workflow, connections, and routing. Customer-service work that requires your staff’s approval or judgment remains with the designated person rather than being assumed to happen automatically. ## Keep a suggestion tied to its source A caller asking for an earlier appointment can create a useful follow-up opportunity. The insight is the request and its context; completing the change is a separate action that depends on staff approval or a configured workflow. Keep those stages distinct when deciding what your team should do next. - Review the call that led to the suggested follow-up and confirm the caller’s actual request. - Identify the person responsible and the business rule that governs the next step. - Ask our team to confirm the supported workflow before assuming an insight can automatically send a message or change a record. ## Working with the Vocalis team The workspace is useful when your team can understand a conversation and its next step without starting over. A caller’s request, the recorded outcome, and the person responsible for follow-up each provide different context. Agree with our team which information people need to see for their day-to-day work. AI summaries and answers help people find and review information. They can omit details or make mistakes, so check the underlying conversation when an answer affects an important commitment. A suggested next step and a completed action are different; bookings, messages, and record changes depend on their own supported workflows. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Answers across conversations with Ask Vocalis Call details and patterns, in the workspace we prepare for you. Category: Platform & AI Reviewed: 2026-10-03 ## A clearer picture of the business Ask Vocalis helps find information across calls and business context, including common questions, mentions of a service, and patterns in appointment enquiries. ## Context behind the answer An answer can relate to a particular caller, topic, or period. Supporting call context helps distinguish a single-call detail from a broader trend. Website examples use fictional figures. ## Set up and supported by Vocalis Our team handles the configuration and any requested changes. An answer or analysis is separate from sending a message, changing a record, or making a booking; those actions require their own confirmed workflow. ## Ask a focused question A question such as “What were callers asking about appointments last week?” gives a clearer scope than a broad request for all business insights. Specify the topic, period, or caller relevant to your task, then review the supporting conversation context where a detail affects a decision. - State whether you need a detail from one conversation or a pattern across several calls. - Include the relevant topic or period and check that the answer refers to the intended context. - Treat any proposed message, booking, or record change as a separate action requiring its own supported workflow. ## Working with the Vocalis team The workspace is useful when your team can understand a conversation and its next step without starting over. A caller’s request, the recorded outcome, and the person responsible for follow-up each provide different context. Agree with our team which information people need to see for their day-to-day work. AI summaries and answers help people find and review information. They can omit details or make mistakes, so check the underlying conversation when an answer affects an important commitment. A suggested next step and a completed action are different; bookings, messages, and record changes depend on their own supported workflows. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Which tools can Vocalis connect to? We scope, connect, and test the systems your workflow needs. Category: Integrations Reviewed: 2026-10-03 ## Documented connections Google Calendar for booking, Gmail for email, and Microsoft 365 / Outlook email are documented connections. Our team handles their configuration with the account owner’s authorization. Outlook Calendar is described as coming soon. ## Other tools and workflows We can discuss CRM, notifications, forms, ticketing, and automation needs. Pipedrive, HubSpot, Salesforce, and Slack are examples of integration candidates, not a promise that every logo on the website is a native connector. ## Implementation handled for you Our team confirms compatibility, access, plan requirements, scope, and costs, then implements and tests the agreed connection. You do not need to build an automation or map fields. Third-party subscriptions or custom integration work may be required. ## Start with a concrete workflow If you want a call summary in your CRM, tell our team whether it belongs on an existing contact, a new lead, or another record. That decision affects contact matching, permissions, and testing. The same principle applies to calendars, email, and notifications: describe the result your staff need first. - Provide the tool and account you use, the desired destination, and the event that should trigger the workflow. - Identify the authorized account owner and any plan or permission restrictions you already know about. - Confirm compatibility, implementation scope, third-party fees, and the expected outcome with our team before relying on a connection. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Google Calendar, connected by Vocalis We prepare the calendar connection used for appointment booking. Category: Integrations Reviewed: 2026-10-03 Availability: Documented connection ## Booking capabilities The published policy describes reading availability and creating, reading, and updating events. Our team configures the intended booking calendar and checks permissions with the authorized account owner. ## Authorization and account changes Provider authorization stays with the account owner; Vocalis guides that approval and handles the surrounding setup. Our team manages the implications of Google’s shared identity for Gmail and Calendar when an account changes. ## Testing and ongoing changes We verify bookings, time zones, and calendar routing. Requests to change or remove the connection go to our team, which checks the effect on any other connected Google product. ## Confirm the intended calendar An account may contain several calendars, and access to the account does not by itself establish the correct booking destination. Tell our team which calendar and appointment workflow should be used. During review, check the event in that destination alongside the time and details communicated to the caller. - Identify the calendar owner, booking calendar, appointment types, and business time zone. - Describe how unavailable time is represented and any location or provider rules that matter. - Before changing a Google connection, discuss its effect on both Calendar and Gmail if they share the same authorization. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Gmail and Microsoft email, configured for you Email organization and draft support, with human approval of sending. Category: Integrations Reviewed: 2026-10-03 Availability: Documented connection ## The email workflow Vocalis’s documented email workflow reads and classifies messages, applies labels, and prepares draft replies. Sending from a connected account requires explicit human approval of a reviewed draft; managed setup does not remove that control. ## We handle the connection Our team arranges the intended mailbox and guides the account owner through provider authorization. We manage the configuration and supported changes to the connection. Gmail shares a Google identity with Calendar; Microsoft email is independent. ## Microsoft calendar availability The documented Microsoft connection covers email. Outlook Calendar is described as coming soon and is not enabled by connecting a Microsoft mailbox. ## Review before sending The documented email workflow can classify messages and prepare draft replies, but a human must review and explicitly approve sending from the connected account. A configured mailbox does not remove that review step. Discuss the types of messages you want handled and which people should be responsible for approving replies. - Identify the mailbox owner, provider, and staff who need to review the workflow. - Share the categories of messages and approved business information relevant to draft replies. - Confirm calendar needs separately: Microsoft email access does not enable the coming-soon Outlook Calendar connection. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # CRM workflows managed by Vocalis Call context connected to useful customer records. Category: Integrations Reviewed: 2026-10-03 Availability: Requires integration setup ## The workflow we scope A CRM workflow may find or create a contact, attach a call summary, record an outcome, or prepare a follow-up. Our team first confirms a compatible connection and the work included in your setup. ## We handle the mapping Vocalis defines the approved trigger, contact matching, fields, record owner, and handling of duplicates and failures. Your business confirms the desired result; our team handles implementation. ## We test the result We validate the agreed workflow with suitable sample data and confirm any third-party or custom-work costs. Copies of information sent to a CRM remain subject to that system’s data controls. ## Define matching and ownership A caller may already be a contact in your CRM. A workflow that creates a new lead every time can differ from the result your business wants. Explain how staff identify an existing contact and who should own the record so our team can scope the supported matching and update behavior. - Describe the trigger and whether the workflow should find, create, or update a record. - List the caller details, summary, outcome, and owner that should reach the destination. - Include duplicate or missing-contact examples and confirm how failures should be handled in the agreed implementation. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Slack and Microsoft Teams notifications Relevant call updates, connected by our team where supported. Category: Integrations Reviewed: 2026-10-03 Availability: Requires integration setup ## Updates that help your people A callback request, new lead, or call needing review can be a useful notification. Our team confirms the supported connection and the events your business wants surfaced. ## An appropriate destination We configure the agreed channel, recipient, context, and level of detail. The destination and its membership must be appropriate for the information being shared. ## A notification has a clear purpose We test the notification workflow. A posted update is not itself a completed callback or live transfer, and the website’s logos do not imply an active connection. ## Share only the useful context A notification should help the right person understand why attention is needed. For example, a callback request can identify the request and its owner without copying an entire sensitive conversation into a broad channel. Discuss the destination and membership with our team before deciding which information should be posted. - Select the events that warrant an update, such as an agreed callback or lead workflow. - Identify the intended channel or recipient and who can see that destination. - Confirm the supported connection and remember that receiving a notification does not complete the underlying customer follow-up. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Automation workflows built by Vocalis We handle the integration work behind the outcome you need. Category: Integrations Reviewed: 2026-10-03 Availability: Requires integration setup ## From business outcome to working connection Our team scopes a concrete task, such as adding an approved summary to a CRM and notifying its owner. We confirm the necessary Vocalis data source and destination capability before committing to the workflow. ## The technical work is ours We handle supported authentication, field mapping, duplicate prevention, retry behavior, and failure handling. Customers do not need to build Zapier or Make flows, write webhooks, or maintain integration settings. ## Availability and scope Automation software may be an implementation option after compatibility and access are confirmed. This is not a claim of a public native Zapier app, universal webhook API, or thousands of turnkey integrations. Any third-party fees and custom work are agreed with your business. ## Scope one outcome at a time A workflow might attach an approved call summary to a CRM contact and notify the record owner. Each step needs a supported source, destination, and clear definition of success. Tell our team how staff should handle an incomplete result so a notification is not mistaken for confirmation that every step succeeded. - Describe the business trigger, destination record, required fields, and final result. - Identify duplicate, missing-data, and failed-action situations that could affect the workflow. - Confirm provider access, any third-party subscription or custom work, and the agreed behavior before launch. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Practice software, job management, forms, and tickets Industry-specific connections scoped and implemented by our team. Category: Integrations Reviewed: 2026-10-03 Availability: Requires integration setup ## The workflow your business needs We discuss the outcome in your existing system, such as a practice booking, a Jobber or Housecall Pro request, an intake link, or a help-desk ticket. Our team investigates the relevant capabilities and access requirements. ## A supported implementation We handle the agreed connection, whether it uses a calendar, approved booking or form link, or a more involved integration. Record updates, waitlists, dispatch, and other complex actions require explicit scope and compatibility. ## Confirmed before launch Our team confirms the available behavior, privacy requirements, costs, and testing. A workflow supported by another receptionist service does not by itself establish native support in Vocalis. ## Explain the action in your existing system Creating a job request, reserving an appointment, and sending an intake link are different workflows. Share which one you need and the system your staff use. Our team investigates the available connection and permissions rather than assuming a practice or job-management tool supports every kind of record change. - Name the software and the specific task the receptionist should help complete. - Describe the record, form, calendar, or approved link involved and the information it requires. - Confirm compatibility, privacy requirements, scope, costs, and the fallback for a task that needs staff attention. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Vocalis information for ChatGPT and Claude A public introduction to the service we manage for you. Category: Integrations Reviewed: 2026-10-03 ## Public company summaries The website’s AI-summary links provide ChatGPT or Claude with a public company overview. They do not connect a Vocalis account or grant access to private calls or workspace content. ## Information designed to be understood The knowledge base, company overview, llms.txt, and structured exports explain Vocalis’s capabilities and managed service. These resources help retrieval but do not guarantee appearance in an AI answer. ## Private connections are separate An authenticated external AI connection would require a separately agreed implementation and authorization managed with our team. A public summary link does not imply an MCP server or access to customer records. ## Understand what the summary link shares The website link opens an external AI service with public company context. It is useful for asking about the Vocalis offering, but it does not sign in to your Vocalis workspace or retrieve customer conversations. A private connection would need separate authorization and an agreed implementation. - Use the company overview and knowledge base to check statements about current Vocalis capabilities. - Distinguish documented connections from examples that still require scope and compatibility confirmation. - Contact our team about a private workflow instead of assuming a public AI-summary link can access account data. ## Working with the Vocalis team Describe the intended result in the destination system before choosing an integration. For example, attaching a call summary to an existing contact is different from creating a new contact or changing an appointment. Our team confirms the source data, destination capability, account authorization, and any costs needed for the agreed result. A provider name or logo does not establish a native connection. Compatibility, permissions, subscriptions, and the behavior available in your account must be confirmed for your workflow. Vocalis handles implementation and testing; an account owner may still need to approve access through the provider’s own authorization process. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # How Vocalis handles information An overview of the existing privacy policy. Category: Privacy & data Reviewed: 2026-10-03 ## Information used for the service The published policy covers contact details, call recordings and transcripts, appointment information, consent records, technical logs, and data from connected Google or Microsoft accounts. ## Use and sharing The policy describes processing for customer businesses and sharing with service providers as needed to provide the service or meet legal requirements. Personal information is not sold, and mobile opt-in data is not shared for third-party marketing. ## Requests handled by our team Privacy questions and access, correction, or deletion requests go to support@vocalis.team. The Privacy Policy remains the complete statement of data-handling commitments. A business contacted by a caller may also hold its own records. ## Identify which organization holds the record A caller’s business may keep information in Vocalis and also in its own scheduling or customer system. A privacy request should make clear which record and organization it concerns. Our team can address the Vocalis service scope, while a customer business or external provider may have separate responsibilities and controls. - Describe the account or business and the information your question concerns. - Use the Privacy Policy for the full statements about collection, use, sharing, and safeguards. - Send access, correction, deletion, or other privacy questions to support@vocalis.team without including unnecessary sensitive details in the initial email. ## Working with the Vocalis team Privacy decisions depend on the information involved, why it is being processed, and who needs access. A contact number, a call transcript, and data from a connected mailbox can have different purposes and controls. Tell our team which workflow or record your question concerns so the response addresses the right scope. These guides provide context for the service, while the published Privacy Policy, Terms of Service, and SMS Terms contain the applicable commitments. Send account-specific questions or requests to support@vocalis.team. A customer business and an external system may hold their own copies of information under separate policies. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Google and Microsoft data controls Permissions and connection changes handled with Vocalis. Category: Privacy & data Reviewed: 2026-10-03 ## Limited Use commitments The published privacy policy commits to Google API Services User Data Policy Limited Use requirements and applies the same restrictions to Microsoft data. Connected-account data is not used for advertising or generalized, non-personalized AI model training. ## Documented AI processing The policy identifies Anthropic Claude through Amazon Bedrock for email classification and drafting on Vocalis’s instructions. This describes that workflow rather than a complete public inventory of every service provider. ## Connection and disconnection requests Our team handles requested connection changes and explains their effect. Gmail and Google Calendar can share authorization, while Microsoft email is independent. Account owners retain control of their provider authorization; the team guides any owner-only approval needed. ## Separate authorization from data use Approving a Google or Microsoft connection permits the configured account workflow under the published policy. It does not establish a broader right to use connected-account information for unrelated purposes. Review the applicable policy and ask our team about the data involved in your specific calendar or email setup. - Identify the provider, connected product, account, and workflow your question concerns. - Check the Privacy Policy for Limited Use commitments and the documented email classification and drafting process. - Discuss connection changes with our team, especially when Gmail and Calendar share Google authorization. ## Working with the Vocalis team Privacy decisions depend on the information involved, why it is being processed, and who needs access. A contact number, a call transcript, and data from a connected mailbox can have different purposes and controls. Tell our team which workflow or record your question concerns so the response addresses the right scope. These guides provide context for the service, while the published Privacy Policy, Terms of Service, and SMS Terms contain the applicable commitments. Send account-specific questions or requests to support@vocalis.team. A customer business and an external system may hold their own copies of information under separate policies. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Text-message consent and opt-out Consent-aware messaging arranged for your approved workflow. Category: Privacy & data Reviewed: 2026-10-03 ## How consent is recorded The published SMS program describes consent through a call, an unchecked web-form checkbox, or a recipient starting a text conversation. Our team incorporates the approved consent wording and supported records into the setup. ## The message program Messages may include appointment confirmations, reminders, and follow-ups. Frequency varies, message and data rates may apply, and consent is not a condition of purchase. The published privacy and SMS terms describe the program. ## Recipient choices Recipients retain the right to reply STOP to unsubscribe or HELP for assistance. These are recipient rights, not customer configuration tasks. Mobile opt-in information is not shared for third-party marketing. ## Make the choice clear to the recipient The web-form example shows an unchecked consent checkbox and the program disclosure. A person should understand the message types, possible rates, and how to stop messages before agreeing. Consent through a call or an inbound text has its own context; our team incorporates the approved wording and supported records into the agreed setup. - Review the exact recipient-facing disclosure and the method used to record consent. - Include the program’s STOP and HELP information, variable frequency, and message-and-data-rate notice. - Use the published SMS Terms and Privacy Policy for the applicable commitments rather than treating this overview as a replacement. ## Working with the Vocalis team Privacy decisions depend on the information involved, why it is being processed, and who needs access. A contact number, a call transcript, and data from a connected mailbox can have different purposes and controls. Tell our team which workflow or record your question concerns so the response addresses the right scope. These guides provide context for the service, while the published Privacy Policy, Terms of Service, and SMS Terms contain the applicable commitments. Send account-specific questions or requests to support@vocalis.team. A customer business and an external system may hold their own copies of information under separate policies. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Retention and deletion requests Data requests coordinated by the Vocalis team. Category: Privacy & data Reviewed: 2026-10-03 ## Retention follows purpose The published policy describes keeping information as needed to provide the service, meet legal obligations, resolve disputes, and enforce agreements, followed by deletion or de-identification. It does not set a universal retention period for every call. ## A direct point of contact Our team handles deletion and account-change requests at support@vocalis.team. We establish the relevant account and scope; customers do not need to work through a configuration checklist. Connected-account data handling remains subject to the policy’s legal retention requirements. ## Other systems may hold copies We explain the effect on shared Google authorization and any connected services in scope. A business or third-party CRM may hold separate copies governed by that organization’s controls. ## Describe the request and its scope A request to disconnect an account is different from a request to delete information already held for the service. Explain the outcome you need and the account involved so our team can address the relevant scope and any applicable retention requirements. The policy does not promise one universal retention period for every record. - Identify the business or account and whether the request concerns access, disconnection, or deletion. - State the information involved without attaching full transcripts or credentials to the initial email. - Consider whether your business or a connected CRM also holds a separate copy governed by that system’s controls. ## Working with the Vocalis team Privacy decisions depend on the information involved, why it is being processed, and who needs access. A contact number, a call transcript, and data from a connected mailbox can have different purposes and controls. Tell our team which workflow or record your question concerns so the response addresses the right scope. These guides provide context for the service, while the published Privacy Policy, Terms of Service, and SMS Terms contain the applicable commitments. Send account-specific questions or requests to support@vocalis.team. A customer business and an external system may hold their own copies of information under separate policies. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Security questions and regulated use Our team confirms the requirements of your workflow with you. Category: Privacy & data Reviewed: 2026-10-03 ## Documented safeguards The privacy policy describes administrative, technical, and physical safeguards, including encryption in transit and access controls. The Vocalis team handles questions about current evidence and applicable agreements for specific security or regulated-use requirements. ## Sensitive workflows We discuss the information involved, access, retention, connected services, and required agreements such as a BAA where applicable. The suitability of a particular integration or channel must be established for that workflow. ## Professional decisions remain with people Our team configures the approved escalation and review paths. AI-generated content can contain errors, and managed configuration does not replace professional judgment or establish regulatory compliance for a customer organization. ## Review the specific workflow A security or regulated-use assessment depends on the information, people, connected services, and agreements involved. A general product description cannot establish suitability for every organization. Bring the requirements for your workflow to our team so the current evidence and necessary agreements can be discussed before you rely on it. - Describe the sensitive information, intended users, destinations, and retention requirements. - Ask about current safeguards and applicable agreements, including a BAA where relevant to your requirements. - Define the human review and escalation path for decisions requiring professional judgment. ## Working with the Vocalis team Privacy decisions depend on the information involved, why it is being processed, and who needs access. A contact number, a call transcript, and data from a connected mailbox can have different purposes and controls. Tell our team which workflow or record your question concerns so the response addresses the right scope. These guides provide context for the service, while the published Privacy Policy, Terms of Service, and SMS Terms contain the applicable commitments. Send account-specific questions or requests to support@vocalis.team. A customer business and an external system may hold their own copies of information under separate policies. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # When do I pay? We finish the receptionist before payment begins. Category: Billing & support Reviewed: 2026-10-03 ## Payment follows configuration Vocalis does not take payment for the receptionist until it is fully configured and you are comfortable with call quality. Our team handles testing, demonstrates the experience, and makes the agreed adjustments before launch. ## If you do not proceed If you decide not to proceed with the receptionist, the Vocalis platform remains free for six months. This applies to platform access, not six months of free AI receptionist calls. ## Plan details explained by our team We confirm the written plan, usage terms, and any third-party or custom integration costs. The live pricing and your agreement govern the offering; the onboarding arrangement does not imply unlimited usage or a refund guarantee. ## Clarify what you are reviewing The onboarding arrangement lets you review the configured receptionist and call quality before payment begins for that service. If you choose not to proceed, six months of free platform access is a separate offering. It should not be interpreted as six months of receptionist calls or unlimited usage. - Review realistic calls and give our team concrete feedback before approving the receptionist experience. - Confirm which service, usage terms, and costs are included in your written plan. - Ask about third-party subscriptions or custom integration work where those affect your agreed setup. ## Working with the Vocalis team A useful conversation starts with the business outcome you need and the part of the service it affects. Call answering, platform access, and a custom connection can have different scope and costs. Our team explains the agreed plan and handles configuration changes; the current pricing page and your written agreement govern your service. For support, include your business name, a short description, and an approximate time if a call or booking is involved. State what you expected and what happened instead. That helps our team locate the relevant workflow without asking you to diagnose technical settings or send credentials in an email. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Pricing and plans Our team helps match the service to your business. Category: Billing & support Reviewed: 2026-10-03 ## The current offering Current prices are published on Vocalis’s live pricing page. Our team explains the appropriate plan, billing options, included usage, and any additional work before you commit. ## The right fit We discuss call volume, locations, booking needs, and integrations, then clarify the scope and costs of your service. Plan or billing changes can be requested through our team. ## Setup is handled for you We configure the receptionist and begin payment only when you are comfortable with its call quality. If you choose not to proceed, the platform remains free for six months. ## Discuss the needs behind a plan Two businesses with similar call volume can have different setup needs because of locations, scheduling rules, or connections. Share those requirements with our team so the plan conversation covers the work you expect. Use the live pricing page and written agreement for current amounts and terms. - Estimate your call volume and describe the locations and business hours involved. - List booking requirements, human handoffs, and any external systems you want connected. - Confirm included usage, billing options, additional work, and how to request a change before committing. ## Working with the Vocalis team A useful conversation starts with the business outcome you need and the part of the service it affects. Call answering, platform access, and a custom connection can have different scope and costs. Our team explains the agreed plan and handles configuration changes; the current pricing page and your written agreement govern your service. For support, include your business name, a short description, and an approximate time if a call or booking is involved. State what you expected and what happened instead. That helps our team locate the relevant workflow without asking you to diagnose technical settings or send credentials in an email. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # When calls are not reaching the receptionist Vocalis investigates the route and resolves configuration issues for you. Category: Billing & support Reviewed: 2026-10-03 ## One point of contact A report to support@vocalis.team starts our investigation. The business name, affected number, and approximate time help us find the relevant issue without asking you to change phone settings. ## We trace the call path Our team checks the agreed routing, carrier behavior, hours, recipients, and available call context. We manage the relevant configuration changes and verify the result. ## Continuity while we investigate When business calls are affected, we coordinate an appropriate temporary fallback with your authorized contact. Credentials and full sensitive transcripts are not needed in a support email. ## Give the team a traceable example If one caller did not reach the receptionist, the affected number and approximate time help distinguish a single incident from a broader routing issue. Explain what the caller heard and what you expected. Our team checks the relevant call path and coordinates an appropriate fallback with your authorized contact if continuity is affected. - Provide your business name, the dialed number, and an approximate date and time with time zone. - Describe whether the call rang elsewhere, reached another message, or ended before the expected answer. - Include whether the issue happens consistently or only in a particular situation; do not email phone-provider credentials. ## Working with the Vocalis team A useful conversation starts with the business outcome you need and the part of the service it affects. Call answering, platform access, and a custom connection can have different scope and costs. Our team explains the agreed plan and handles configuration changes; the current pricing page and your written agreement govern your service. For support, include your business name, a short description, and an approximate time if a call or booking is involved. State what you expected and what happened instead. That helps our team locate the relevant workflow without asking you to diagnose technical settings or send credentials in an email. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # When a calendar or email connection needs attention Our team investigates, repairs, and verifies the supported connection. Category: Billing & support Reviewed: 2026-10-03 ## We identify the issue Vocalis checks which connection and workflow are affected, including the intended account, destination, and permissions. A short description and approximate time help us locate the problem. ## We handle the repair Our team manages reconnection and routing changes. If the provider requires the account owner to authorize access again, we guide that approval; you do not need to diagnose OAuth, tokens, or calendar settings. ## We verify the result We test the affected booking or email workflow before confirming the repair. Outlook Calendar remains separate from Microsoft email and is described as coming soon. ## Describe the affected action A connected account can appear available while a particular booking or email action still needs attention. Tell our team what you were trying to do, the intended destination, and the outcome. This lets the investigation focus on the workflow rather than asking you to change permissions or diagnose technical settings. - Identify the calendar or mailbox and the approximate time of the affected action. - Describe the expected event or draft and what appeared instead, including any visible error wording. - If provider authorization is needed again, use the provider’s approval flow with our team’s guidance rather than emailing credentials. ## Working with the Vocalis team A useful conversation starts with the business outcome you need and the part of the service it affects. Call answering, platform access, and a custom connection can have different scope and costs. Our team explains the agreed plan and handles configuration changes; the current pricing page and your written agreement govern your service. For support, include your business name, a short description, and an approximate time if a call or booking is involved. State what you expected and what happened instead. That helps our team locate the relevant workflow without asking you to diagnose technical settings or send credentials in an email. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html --- # Contacting Vocalis Your point of contact for setup, updates, and support. Category: Billing & support Reviewed: 2026-10-03 ## Reach the team The Vocalis team is available at support@vocalis.team for business updates, configuration requests, integration questions, support, and privacy matters. ## Tell us the outcome you need A business name and a short description are enough to start the conversation. We gather any further details and handle the technical work. No response-time service level is promised by this knowledge base. ## Privacy and legal questions Email support@vocalis.team with privacy or legal questions. The Privacy Policy and Terms of Service describe our legal commitments. ## Make the first message useful A short, specific message gives our team a good starting point. For example, a request to change after-hours routing should identify the business, the new destination, and when the change should apply. A reported problem should describe what happened and what you expected, with an approximate time if relevant. - Include your business name, the topic, and the outcome you need. - For a configuration change, provide the new approved information and any affected location or service. - For a privacy or legal question, identify the relevant account or policy; keep passwords and unnecessary sensitive caller information out of the initial email. ## Working with the Vocalis team A useful conversation starts with the business outcome you need and the part of the service it affects. Call answering, platform access, and a custom connection can have different scope and costs. Our team explains the agreed plan and handles configuration changes; the current pricing page and your written agreement govern your service. For support, include your business name, a short description, and an approximate time if a call or booking is involved. State what you expected and what happened instead. That helps our team locate the relevant workflow without asking you to diagnose technical settings or send credentials in an email. Contact: support@vocalis.team Privacy policy: /privacy.html Terms of service: /terms.html