BYstudio. Illustrative website-to-CRM brief
21 October 2026. Not production data or a completed client project.
Source: https://bystudio.ru/en/solutions/website-crm-integration-brief/

Goal: transfer one validated Service enquiry form to the selected CRM.
Direction: website -> CRM only. Payments, files and old-record import excluded.

Fields:
Name: Test customer -> contact name; optional text.
Email: client@example.com -> contact email; required, validate format.
Task: Service website needed -> deal description; required text.
Source: Website -> agreed CRM field, set by the server.
Event: demo-enquiry-001 -> log and agreed CRM-record mapping.
Verify field names, length limits and permissions before launch.

Route:
Agreed pipeline, New enquiry stage; process owner assigns the manager.
These are illustrative labels, not API codes. Name the employee before acceptance.

Retries:
The same demo-enquiry-001 event does not create a second deal.
A new event with the same email creates a new deal linked to the existing
contact under the agreed rule. Reconcile before retrying a lost response.

Failure:
Save an accepted enquiry in agreed durable pending storage. Temporary failure
starts bounded retries. Interval and limit need agreement. A technical owner
corrects invalid fields or access. After exhaustion, an assigned employee
handles the enquiry manually. Agree alert recipient and channel before work.
Only confirm receipt to the visitor after durable storage is established.

Test-environment acceptance:
1. New submission: one deal, correct fields, source, stage and employee access.
2. Invalid email: clear error and no invalid deal.
3. Repeated event: one deal remains.
4. New event with the same email: new deal linked to the existing contact.
5. CRM failure: pending enquiry is visible; recovery leaves one deal.
6. Lost response: reconcile the result without creating an extra deal.

Complete before launch: CRM, fields, permissions, employee, retry interval and
limit, log retention, alert channel, acceptance owner and support.
Credentials and customer records are not part of this example.