How a configurator can connect with Daktela

Customer communicationAssessed per project

Daktela is a Czech contact centre that brings calls, chat, email and tickets into one place. It has a REST API, developer SDKs and ready-made connections to webshops and accounting systems.

What a configuration could hand over

When a customer calls shortly after submitting a configuration, the agent should not have to go looking. The contact and the enquiry can be waiting in Daktela, so the call starts from the actual product and its dimensions. What is shown and what returns to the CRM afterwards is agreed during implementation.

  • CRM contact

    The customer could become a new CRM contact, or update an existing one, with name, phone and email, so the agent can find them during a call without searching the mailbox.

  • Account

    If the enquiry comes from a company, such as a builder, the contact can be linked to its account so that its further enquiries sit together.

  • Ticket

    A submitted configuration can open a ticket in a chosen category, with dimensions, material, price and a link to the 3D view in the description or in custom fields.

  • CRM record

    For repeat sales, a CRM record of your own type, such as “Pergola enquiry”, can keep the history of one customer’s configurations.

What we need to connect it

  1. The connection would use a dedicated Daktela user with rights only to the modules it needs; you pass us that user’s access token from the user details by a secure route.

  2. It would run over the REST API v6 of your instance, whose address and version we check first.

  3. You create or adjust the custom fields for tickets and the CRM in administration, and we agree the mapping from the configuration in a table.

  4. Trial tickets would go to a test category so they do not distort agent statistics.

Worth deciding up front

  • In Daktela, custom fields are shared by tickets, CRM contacts, accounts and records, so changing a field in one form changes it everywhere; we name the configurator fields so they do not clash with existing ones.
  • For a repeat enquiry from the same number you need to decide whether a new contact is created or the existing one updated, or the CRM fills with duplicates.
  • Removing or changing a select field option can make stored values inaccessible, so the list of products and materials is agreed in advance.

Questions about this connection

Will the agent see the configuration as soon as the customer calls?

If the configuration is stored with the contact or ticket, the agent can have it at hand during the call, together with the link to the 3D view. Exactly where it shows depends on your Daktela forms and is designed during implementation.

The ticket can be opened in whichever category you assign to that product in Daktela. The rules for which agent receives it then stay in your Daktela; the configurator does not change them.

Other integrations

Put Daktela to work in your sales.

Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.

treede is not an official partner or reseller of the systems named here. All names and marks belong to their owners. Integration options are verified during implementation against the system interface and version. Daktela official site