Skip to content
Victoria AI
Integrations

Victoria reads from and writes to your management system.

The agent checks stock and prices, builds the quote and returns the document to your management system. No migration, no double entry, no parallel system.

Book a meetingSee security and data

If your system is not integrated, we build the connector within the onboarding fee.

The technical contract

What it reads and what it writes in your system.

We define it during discovery, field by field. The agent only reaches what you enable for it.

What Victoria reads from your system

  • Live catalog and prices

    The quoting tool works with the real products and prices in your management system, not with an outdated copy.

  • Price list per customer

    Once the customer is identified, their price list and the account’s real VAT rate are applied.

  • Customer record

    The lead is matched to the customer in your system by CUIT (tax ID), phone or legal name, resolving ambiguities before operating.

  • Documents from the history

    The documents in the management system are brought into the customer’s history inside Victoria CRM.

What Victoria writes in your system

  • Quotes

    The quote built in Victoria CRM is sent to your management system, with its line items, quantities and prices.

  • Generated documents

    If your system generates the quote PDF, we delegate it. If it does not support that, Victoria generates it with your company logo.

  • Customer data

    Contact data is created and updated according to what the company enables, with every change recorded.

  • Operational actions

    Everything we give it a tool for: entering the order, modifying it, canceling it, arranging the shipment and logging the case.

Your company defines the scope. You decide what is read, what is written and what needs human approval before it runs.

See security and data
Connected systems

What Victoria connects to today.

Every integration has its state declared. If the one you need is in grey, it gets built.

  • Available
  • In progress
  • Custom-built

  • Management systems in the market

    Available

    There are connectors in production with several ERPs in use today: catalog, prices and documents synced with the quoting tool.

  • Variants with their own schema

    Available

    The same ERP changes its data schema from one installation to the next. The connector adapts to yours, without touching your database.

  • Victoria’s native ERP

    Available

    If you have no management system, Victoria’s own ERP covers catalog, prices and documents.

  • Your system

    Custom-built

    We build the connector within the onboarding fee.

    See how
Channels

Wherever they write to you, Victoria replies.

Every channel lands in the same inbox, with a single history per customer.

WhatsApp with multiple numbers and multiple accounts, with the 24-hour window managed by the system.

See the omnichannel inbox
Custom integration

If the connection does not exist, we build it.

There is no closed list of compatible systems. There is a way to connect them.

  • "My management system is not on the list"

    The system you use is in-house, is old or was built by a local vendor, and has never been connected to anything.

    Victoria solves it

    The connector is built within the onboarding fee. We review the available API or database and define the scope before starting.

  • "I do not know who can build that connection"

    Your system vendor does not reply or your team has no time.

    Victoria solves it

    The connector can be built by your team, by your system vendor or by us. We define who does it based on who has the documentation.

  • "I do not want to open up my whole system"

    Giving full access to an outside vendor is not an option.

    Victoria solves it

    Only what is used is enabled. An integration user with minimum permissions, data isolated by company and an audit trail of every action.

See the implementation process
Extensibility

If you need to connect something else, there is a way.

Beyond the native integrations, each company has its own API key and can fire webhooks from its automations.

  • A dedicated API per company

    Each company has its API key to integrate Victoria with its own developments.

  • Outbound webhooks from the automations

    Any flow can call an external system with the method you need (GET, POST, PUT, PATCH or DELETE), your own headers and the body you define.

  • You choose the data that travels

    Suggested fields such as lead ID, name, phone, email, source, status, funnel, event type, timestamp and chat ID, or the free fields you define.

  • HTTPS required

    An unencrypted address is rejected at configuration time, with a warning that the customer data would travel exposed. It is not optional.

Each company’s data lives isolated, with permissions per user and per area, and every action is audited.

See the CRM integrations
Keep reading

Before connecting, this matters too.

Next step

Tell us which system you use.

In the discovery meeting we review your management system, define what is read, what is written and whether the connector needs to be built.

Book a meetingChat on WhatsApp

If your system is not integrated yet, the connector is part of the onboarding fee.

WhatsApp