# ELMA365

Connect ELMA365 and save a validated application mapping before adding actions. The bot uses the selected company, fields, assignees and permitted stages.

# Find a contact

Parameters: Exact phone number or email.

Result: Matching contacts or no match.

# Create or update a contact

Parameters: Name, phone or email, an existing ID when updating, and consent to save.

Result: Contact ID and whether it was created or updated.

# Create a deal or lead

Parameters: Contact ID, title, mapped optional fields and consent.

Result: Record ID and stage in the selected application.

# Change deal stage

Parameters: Deal ID, a permitted stage and consent.

Result: Confirmed stage.

# Create a task

Parameters: Subject, an exact future deadline with timezone, related contact or deal, permitted assignee and consent.

Result: Task ID and link.

# Add a note

Parameters: Record type, record ID, text and consent.

Result: Comment ID in the record's feed.

# Get a CRM link

Parameters: Record type: contact, deal or task; its ID.

Result: Link to an accessible record in the connected company.

Optional fields depend on the mapping. The bot cannot send arbitrary fields or change the application during a conversation. Changing a mapped deal amount requires separate consent. Money fields support RUB, KZT, USD and EUR, with no more than two decimal places. The currency must match the ELMA365 field configuration.

# Recommended sequence

1. Ask for contact details and search by exact phone or email.
2. Escalate multiple matches or conflicting phone/email results to a manager.
3. Obtain consent and create or update the contact.
4. Check active deals and create a request according to the configured policy.
5. Add a note, change a permitted stage and create a related task when needed.
6. Report success only after the result is confirmed, and provide the record link.

Use record IDs returned by preceding actions. A deadline must include date, time and timezone, for example 2026-10-15T15:00:00+03:00; choose a future date when testing.

Preview reads ELMA365 and validates parameters without creating or changing records. It does not replace a real bot conversation test.

If an ELMA365 response is lost, ChatRex blocks another write and checks the outcome where it can be established unambiguously. Notes and unresolved operations may require support. A new request with different parameters is not a safe replay.

A note is an internal comment in the selected record's feed. It does not message a customer through Lines; the connected ChatRex channel delivers the chat reply.