A new enquiry joins an existing relationship
This example shows the module’s role in a hotel process. We define the source scope and available actions for each implementation.
Different email address, same company
The organiser sends an enquiry from a new address. The CRM contains previous events and an assigned account owner, but automatically creating another company would cause a duplicate.
Data for the sales team to check
The integration provides the matching record and its history. The qualification module uses this context, while the CRM is updated according to an approved rule. An uncertain match is not automatically linked to an existing contact.
- Relationship context
- Record owner
- Controlled activity update
What does this module cover?
We connect specific objects and fields, such as contacts, companies, deals, stages and activities. There is no need to share the entire CRM. Available operations depend on the system, licence and integration account permissions.
Relationship history
AI can use previous events and contact history instead of analysing an enquiry in isolation.
Agreed write access
Notes, tasks or stage changes are added only to permitted fields.
Duplicate control
Stable identifiers and matching rules help avoid creating the same company more than once.
How do we launch the solution?
Data mapping
We define the meaning of fields, identifiers, owners and the scope of operations.
Start with read access
We test record matching and context quality on a limited data set.
Enable approved changes
We add writing with an activity log, error handling and safeguards against repeated operations.
What goes into the module and what comes out?
We separate source material from the tool’s output. This helps subsequent modules understand which context they can use.
What does AI use?
- CRM and integration account
- Field and stage map
- Matching and permission rules
What does the team receive?
- Customer context for AI
- Permitted record operations
- Log of completed updates
Permissions and decisions remain with the hotel
Before launch, we agree data access, responsible people and how exceptions will be handled.
The hotel selects the fields available for reading and writing and defines which changes require approval. The record owner, activity history and error information remain visible to the team.
The integration is not an independent sales agent. Research, lead allocation and decisions about the next contact belong to the modules that use CRM data.
What changes in day-to-day work?
Agreements can be added to the correct record without manually copying them between applications.
Several AI tools use the same sales context.
Which sources and tools do we connect the module to?
You can start with read-only access. Automatic writing is enabled only after rules, permissions and connection-error handling have been agreed.
Related process elements
Its place in the implementation journey
These links come from the roadmap. Requirements form the basis of each node, while enrichments extend its capabilities. This does not mean that all subsequent modules must be launched at once.
Modules that require this element
See other connections (2)
Modules this element enriches
Frequently asked questions
Can AI overwrite customer data?
Only if the operation is предусмотрed and authorised. At first, writing can be disabled entirely or every change can require approval.
Does the integration work with every CRM?
We assess the scope for each specific system and its configuration. We do not assume that all fields and operations will be available.