Find the help you need.

AYWA lets you build voice agents that can receive or place calls.

Core capabilities

• Answer and route inbound calls
• Run outbound campaigns
• Qualify an enquiry or prospect
• Book appointments and trigger actions in your tools

Configuration, tests, calls and results are managed from your AYWA workspace.

1. Open Agents and create an agent.
2. Define its type, identity and spoken language.
3. Describe its mission and add the required capabilities.
4. Choose a voice.
5. Test its behaviour before publishing.

The agent’s spoken language is independent from the interface language.

Open the editor and check the greeting, language, responses, interruptions and how the conversation ends. Use the browser test to try the conversation with your microphone. Use a phone test to check a live transfer and what happens when nobody answers. Check tool results before publishing.

Active plans, prices, included minutes and overage rules are shown under Settings → Billing.

Check that page for the plans and terms currently available to your account.

Open Settings → Billing, select the plan you want and review the summary before confirming.

The confirmation screen shows the effective date, any prorated charges or credits, and the amounts that will apply.

The dashboard and Settings → Billing show minutes used, available allowance and any overage costs.

Call usage may take a short time to finalise after the call ends.

Behaviour depends on the active plan: some plans stop service at the allowance, while others permit billed overage.

Check Settings → Billing for the rule and rate applicable to your account.

Open Settings → Billing to view your subscription, manage the payment method and access available invoices.

Refer to the issued invoice for the final taxes and totals.

Manage cancellation from Settings → Billing.

Before confirming, review the access end date and retention information shown in the flow.

When a trial is available, its duration, allowance and status appear in the application banner and under Settings → Billing.

If general documentation differs, use the trial details shown in your account.

Describe the mission, boundaries and information the agent needs. Use the writing assistant to structure that context, then review the result before publishing.

Avoid duplicating rules already handled by capabilities or tools. Short, coherent instructions are more reliable.

In the editor, choose the spoken language first, then preview compatible voices.

The agent voice and language are call settings. They do not change when you switch the AYWA interface language.

Add destinations to the directory, then enable transfer for the agent and select the allowed destinations.

Test routing, the dialled number, the transfer announcement and behaviour when the destination does not answer.

Upload documents under Documents, check their indexing status, then assign them to the agent.

Use clear, current sources. Then test a question whose answer appears in each important document.

Published status determines whether the active configuration can handle calls. After a change, publish the new version and check its state in the agent list.

Pausing an agent does not delete its configuration or history.

Duplicate an agent to reuse a configuration baseline, then update its identity, tools, destinations and documents.

Before publishing, make sure no source-agent-specific data remains by mistake.

Choose the calendar managed by AYWA, if available, or select a connected Google or Microsoft calendar. Enable availability lookup and appointment creation. Check the calendar, working days, duration and time zone.

Test a real time slot and check the booking. The agent should only confirm the appointment once the booking tool has completed successfully.

Check the agent’s sending mode, recipient address and campaign or post-call email settings.

Depending on the setup, a confirmed booking can generate a calendar invitation or an email with an invitation attached. Summary emails depend on the sending rules you configure. Test with your own address: content, appointment time, sender and delivery result.

An administrator can configure a compatible existing line or search for a number in supported countries. Check features and price before confirming.

Documents and carrier approval may be required depending on country and number type. Wait for activation, select the line in the agent’s telephony settings and test a call. For SMS, check messaging support and activation.

1. Open Campaigns and choose an objective.
2. Describe the offer or mission and add your sources.
3. Choose the topics to cover and the questions to ask for that objective.
4. Attach an agent, prospects and required tools.
5. Test before scheduling or launching.

Campaign language controls the conversation; interface language does not change it.

Import a supported file, review the preview and map columns before confirming.

International numbers should preferably use E.164. Local numbers use the phone country set for your workspace, regardless of the interface language.

Set campaign days, calling windows, pacing and retry attempts.

Check the displayed timezone. It comes from your campaign and workspace settings, regardless of the interface language.

The Calls page lists calls available to your organisation. Use date, agent, campaign and status filters to narrow the list.

Metrics and artefacts may take a short time to finalise after a call ends.

The dashboard and reporting aggregate volume, duration, statuses and outcomes for the selected filters.

Check the period, organisation and filter scope before comparing indicators.

From Calls, review the available timeline, transcript, recording, estimated costs and tool results. Some details become available after the call ends.

If a transcript appears incorrect, compare it with the recording when available. To check a booking or sent message, review the action result and, if needed, the connected tool.

Open Voice bank, start the cloning flow and read the recording script in the selected language.

Use a stable microphone, a quiet room and only the voice of a person who has explicitly authorised cloning.

Wait until the voice is ready, preview it and assign it to a compatible agent.

Test several sentence types before publishing. A voice is an agent setting; changing interface language does not replace it.

Browse integrations by use. Open a tool’s page in Integrations to review what it supports and complete the connection.

• CRM and sales : HubSpot, Salesforce, Pipedrive, Zoho CRM, Freshsales, ActiveCampaign, Microsoft Dynamics (coming soon).
• Calendars and appointments : Google Calendar, Microsoft Outlook, Calendly.
• Customer and IT support : Zendesk, Intercom, Freshdesk, Jira, Atera, ServiceNow.
• Projects and tasks : monday.com, ClickUp, Asana, Trello, Todoist.
• Email and messaging : Gmail, Microsoft Teams, WhatsApp Business, SMS AYWA.
• Documents and spreadsheets : Google Drive, Google Docs, Google Sheets.
• E-commerce : Shopify, WooCommerce.
• Billing and payment follow-up : Stripe, Pennylane, Sellsy, Chargebee.
• Prospect research : Clay (in prospects, when enabled).

For each tool, check its available actions, connected account and permissions. The guide for that category explains how to set up and verify your workflow.

In the new release, every connector can be used during a call. The agent retrieves information, performs authorized actions and uses the result to continue the conversation. The operations available still depend on the connected tool.

Example uses

• Find a customer record and use its details to handle the request.
• Check availability and book an appointment agreed with the caller.
• Update information or create a support ticket during the conversation, when the connector supports that action.

Prepare your agent

1. Connect the relevant account in Integrations.
2. Define which connectors and actions this agent can use during calls.
3. Explain in its instructions when to consult the tool, which details to collect and when to ask the caller’s permission before making a change.
4. Test a complete conversation, then check the action’s result in the connected tool.

The agent should only say an action is complete after the tool confirms success. If details are missing or the tool fails, plan a follow-up question or a handover to your team.

Post-call actions remain useful for saving a summary, passing on the outcome or starting follow-up once the conversation ends.

Assign an integration to the agent and choose supported actions: updating a CRM record, adding a note, sending a message, opening a ticket or sending information to an external service.

Define conditions and information to send, then enable the rule. Execution depends on integration status and account permissions. Test the workflow and review the action history to check successes or investigate failures.

HubSpot, Salesforce, Pipedrive, Zoho CRM, Freshsales and ActiveCampaign connect your sales records to AYWA.

1. Find your CRM in Integrations and follow the connection method shown: account authorization or the requested credentials.
2. To import contacts, select the source and scope, map the fields and review the preview before running the import.
3. To record a call outcome, assign the connector to the agent and configure one of its available post-call actions.
4. Use a test record and check the information received in your CRM.

Contact imports and post-call updates are configured separately. Microsoft Dynamics is also listed in the catalogue as coming soon.

AYWA’s support integrations include Atera, Zendesk, Freshdesk, Jira, ServiceNow and Intercom.

1. Connect the account your support team uses.
2. Select an action supported by that connector: creating a ticket, passing on context or updating a contact, depending on the tool.
3. For a post-call rule, choose when it runs and which details to send: the request, relevant contact details, summary and priority if offered.
4. Select the required project, group or destination, then check the result in your support tool.

Operations vary by connector. Do not assume Intercom offers the same ticketing actions as Atera or Zendesk.

monday.com, ClickUp, Asana, Trello and Todoist help your team organize follow-up work in its own tools.

Connect an account from Integrations, then review the actions available on its page. If post-call task creation is offered, choose the destination board, project or list and set the title and details to include.

Test in a dedicated workspace and check the destination, content and permissions. If an action is missing, confirm the setup with AYWA before building a workflow that depends on it.

The catalogue includes Gmail, Microsoft Outlook, Microsoft Teams, WhatsApp Business and AYWA SMS. Setup depends on the channel and the message you want to send.

• Email: connect a Google or Microsoft account, then check the sending mode selected for the agent or campaign.
• WhatsApp Business: provide the requested connection details and choose a messaging action when offered.
• AYWA SMS: select an eligible AYWA Calls + SMS number and enable messages for the agent.
• Microsoft Teams: connect your account and check its available operations before defining your workflow.

Test with your own address or number, then check the recipient, content and sending result. Connecting an account does not automatically create a messaging rule.

Google Drive, Google Docs and Google Sheets are listed in the catalogue. Connect them using a Google account with access to the files you need.

1. Open Integrations, choose the service and authorize the correct account.
2. Review the available operations and select any files, folders or sheets required by your setup.
3. Test with a dedicated document before using your working data.

Connecting Drive does not automatically add every document to the agent’s knowledge. For a knowledge base, also check the sources configured in the agent editor.

Connect your Shopify or WooCommerce store from Integrations, using the access details requested on its page.

To prepare a campaign, select the available contact source, map its fields and check the preview before importing. To send back a call outcome, separately configure the post-call action offered for your store.

Check the behavior with a test contact. An e-commerce connector does not automatically support every store operation: confirm the available action before planning an order, stock or payment change.

Stripe, Pennylane, Sellsy and Chargebee can supply billing data for payment follow-up campaigns. Some CRMs also offer a source compatible with this use.

1. Connect the tool from Integrations.
2. In your payment follow-up campaign, select that source and define the relevant invoices or filters.
3. Review the preview: customer, contact details, reference, amount, due date and payment link when supplied.
4. Check how paid invoices are handled and define exit conditions before activating the campaign.

The connection supplies context for follow-up. Check invoice details and status in your billing tool before starting the campaign.

Clay has a dedicated workflow in Prospects when enabled for your workspace. A shortcut may also appear in the integrations catalogue.

Open that workflow, connect your own Clay account with the requested access details and define the companies or contacts you want to find. Review the results, available contact details and any Clay costs before adding prospects to a campaign.

Finding prospects, adding them to AYWA and starting a campaign are separate steps. Check contact details and relevant information before assigning a campaign to your agent.

Open Integrations, choose Google Calendar and complete authorisation with the correct account.

Then select the calendar used by the agent and test both slot lookup and real appointment creation.

Open Integrations, choose Microsoft and complete authorisation with the account that owns the calendar.

Review granted permissions, select the target calendar and run an end-to-end test.

Managed mode uses the calendar and email services provided by AYWA when available for your workspace. Select it in the agent’s communication settings.

Set availability, duration and time zone, then test a booking and its invitation. To take account of events in your usual calendar, choose connected mode and assign that calendar.

With the extension installed, sign in to AYWA and connect your session from the Companion panel. Open a LinkedIn profile, post or search and review the captured context.

Send it to Sales Research, then create a prospect with or without a campaign when available. Check the information, target campaign and review mode before adding anyone.

Under Settings → Users, enter the person’s address, choose a role and send the invitation.

Check the displayed organisation before sending. The invitation grants only the permissions of the selected role.

Roles determine which pages, resources and actions each member can access.

Use least privilege: grant only required permissions, then test with an account holding that role.

The directory structures departments, contacts and destinations that inbound agents can search or call.

Avoid duplicate numbers, use clear labels and retest every critical transfer after changes.

Check that the agent is published and active, the line points to the right agent and the plan still allows calls.

For a browser call, also check microphone permission. For a phone call, review call status and logs.

Check calendar integration status, enabled agent tools, target calendar, availability and timezone.

Test slot lookup and creation separately. Call details must show tool success before any spoken confirmation.

Check the email address, verification state and expected organisation. Retry in a private window to rule out a stale session.

If it persists, send support the time, URL and error message without sharing your password.

From the sign-in page, choose Forgot password, enter your email and open the link you receive.

Use the newest link. If no email arrives, check spam and the address entered.