Skip to main content

Voice Actions: Register Information Faster with Sage Copilot

Use Sage Copilot to create new records or complete existing information using natural language. Describe what you need using text, voice, images or documents, and let Copilot prepare a proposal for you to review before saving it in Sage Sales Management.

Written by Training

What are Voice Actions?

Voice Actions are a Sage Copilot capability designed to help you capture information in Sage Sales Management more quickly and naturally.

Instead of completing every field in a form manually, you can simply describe what you need using your own words. Sage Copilot interprets your request, identifies the relevant information, and prepares a proposal to complete the corresponding record.

Its goal is to reduce the time spent on administrative tasks, help you keep your CRM information up to date, and allow you to focus on selling.

In addition to completing information, it can also help you analyse different sources, resolve ambiguities, and prepare proposals based on the available context.

Although its name refers to voice, you can also use text, images and PDF documents to provide the necessary context. Sage Copilot combines all the available information to generate a single proposal.


How it works

Voice Actions use artificial intelligence to interpret your request and understand the task you want to perform.

Depending on the context, Sage Copilot can analyse:

  • Text.

  • Audio.

  • Images.

  • PDF documents.

  • Publicly available information from the Internet, where supported.

Once the information has been analysed, Sage Copilot identifies the relevant data, organises it within the appropriate form, and prepares a proposal for you to review before confirming the changes.

This process ensures that you remain in control of the information stored in your CRM.


What you can do

You can currently use Voice Actions with:

  • Companies.

  • Contacts.

  • Activities.

  • WhatsApp Activities.

  • Events.

  • Tasks.

  • Opportunities.

  • Orders.

Depending on the context, Sage Copilot can help you create new records, complete existing information, analyse different sources of information, and prepare proposals to speed up your daily work.


Use cases

Voice Actions can help you throughout your daily work. These examples show how Sage Copilot combines different sources of information to prepare a proposal that you can always review before saving.

Create a company from a description

If you only know a few details about a company, you can describe it using natural language.

For example, you can provide its name, the sales status you want to assign, and any other relevant information.

Where available, Sage Copilot can enrich the company record using publicly available information.

During the process, it also tells you:

  • Which fields were completed automatically.

  • Which sources were used.

  • Whether any discrepancies were detected between different sources.

This allows you to review each value before creating the record.


Complete a company record using multiple sources

You can also combine different types of information in a single request.

For example:

  • A written description.

  • A PDF document.

  • Publicly available information.

Sage Copilot analyses all available sources together, identifies matching information, validates the available data, and prepares a single proposal to complete the form.

If it finds information that is more reliable or more up to date than the original input, it lets you know so that you can decide which information to keep.


Prepare an order with intelligent recommendations

Voice Actions can also assist you while creating sales documents.

In addition to completing information, Sage Copilot analyses the available context to help you make decisions throughout the process.

For example, it can:

  • Identify the most suitable product.

  • Resolve potential ambiguities.

  • Explain why a particular option has been suggested.

  • Recommend alternatives where several options are available.

Once you have reviewed the proposal, you can ask Copilot to complete the form using your selected option.


Create an activity from an image

You can also create activities using images as a source of information.

For example, you can attach a conversation screenshot, an email, or any image containing relevant information.

Sage Copilot analyses the content, identifies the required information, and proposes completing the activity automatically.

If the activity includes dynamic fields configured in Sage Sales Management, Copilot also attempts to identify and populate those fields whenever sufficient information is available.


Review the proposal before saving

Voice Actions are designed to help you prepare information, not replace your judgement.

Before saving any record, you can review all the proposed information.

When multiple sources have been used, Sage Copilot shows you:

  • Which information was completed automatically.

  • Which sources were used.

  • Any discrepancies it detected.

  • Any recommendations where several alternatives are available.

This approach helps reduce repetitive tasks while ensuring that you remain in control of the information ultimately stored in Sage Sales Management.


Best practices

To achieve the best results:

  • Describe the situation naturally.

  • Provide all relevant information in a single request whenever possible.

  • Attach documents or images if they provide additional context.

  • If Sage Copilot asks you to clarify any information, answer its questions to improve the proposal.

  • Always review the proposal before saving it.

The more context you provide, the more accurate Sage Copilot’s assistance will be.


Current limitations

The current version includes several limitations designed to ensure data quality and provide a safe experience when creating or updating records.

At present, Voice Actions:

  • Create one record per request.

  • Complete only empty fields in existing records.

  • Respect the user’s permissions.

  • Work within the entity from which the action was initiated.

  • Use the language configured for the current user throughout the interaction.

These capabilities will continue to evolve in future releases.

Did this answer your question?