Customer record management

Store contacts and status in the Customer profile and link Conversations, Reservations and Purchases to that customer.

Acceptance

Verify source identity reconciliation and history linkage.

Boundary

Verify linked customer records separately from staff workspaces (Dashboard and mobile app) and ad-account metrics (Advertising campaign management).

Read customer conversations, reservations, and purchases

[blocked]

Find the customer in the current organization and compare phone or channel identifiers.

Starting conditions and inputs

Identify the customer ID and time range.

Values for this task

entry_url, customer_id, period

Command sequence

text

open "$entry_url" && snapshot -i
click "$customer_row" && snapshot -i
get text body
click "$relationship" && snapshot -i
get text body
click "$source_link" && snapshot -i
get text body

open "$entry_url" && snapshot -i
click "$customer_row" && snapshot -i
get text body
click "$relationship" && snapshot -i
get text body
click "$source_link" && snapshot -i
get text body

Ref targets and expected results

#	Command / ref	Target and verification
1	`click` `$customer_row`	Customer record matching the identifier
2	`get text`	Compare external customer ID and contact.
3	`click` `$relationship`	Conversation, reservation or purchase relationship to inspect
4	`get text`	Read linked customer ID, time and state.
5	`click` `$source_link`	Source record link to compare
6	`get text`	Compare relationship values with the source record.

Check the result

Duplicates and unlinked records are distinguished from customer activity.

Resuming after interruption

Read the same source IDs again. Check organization and time range before treating an empty result as missing data.

[blocked]

Select the customer

Find the customer in the current organization and compare phone or channel identifiers. Do not select by name alone. Confirm scope and permissions before reviewing activity across branches.

[blocked]

Review activities

Inspect related conversations, reservations, and purchases. Distinguish creation time, appointment time, and payment time. Do not count cancelled reservations as successful outcomes.

[blocked]

Open source records

Open the source activity for its status and saved details. Read inquiry text from conversations, schedules from reservations, and amounts from purchases. A summary alone does not establish completion.

[blocked]

Investigate missing links

Check filters, period, organization access, and the source customer link when activity is missing. Have an authorized staff member correct wrong links using the identity rules. Do not invent completed activity when no source exists.

Create and update customer profiles

[blocked]

Search for existing customers by phone or channel identifier before creating one.

Starting conditions and inputs

Have customer identifiers and verified profile values.

Define how customer and transaction records connect

Values for this task

entry_url, organization_id, customer_id, profile_values, customer_lookup, field_value

Command sequence

text

open "$entry_url" && snapshot -i
click "$filter" && snapshot -i
click "$name_condition" && snapshot -i
fill "$name_input" "$customer_lookup" && snapshot -i
get text body
click "$customer_row" && snapshot -i
fill "$customer_field" "$field_value" && press 'Tab' && snapshot -i
reload && snapshot -i
get value "$customer_field"

open "$entry_url" && snapshot -i
click "$filter" && snapshot -i
click "$name_condition" && snapshot -i
fill "$name_input" "$customer_lookup" && snapshot -i
get text body
click "$customer_row" && snapshot -i
fill "$customer_field" "$field_value" && press 'Tab' && snapshot -i
reload && snapshot -i
get value "$customer_field"

Ref targets and expected results

#	Command / ref	Target and verification
1	`click` `$filter`	Customer table filter button
2	`click` `$name_condition`	Name condition (name) in the customer table
3	`fill` `$name_input`	Customer identifier input
4	`get text`	Compare existing customer ID and contact.
5	`click` `$customer_row`	Customer record to edit
6	`fill` `$customer_field`	Customer field being changed
7	`press`	Leave the field input.
8	`reload`	Reload the same customer record.
9	`get value` `$customer_field`	Compare the edited input with the expected value.

Check the result

Organization and customer IDs match and saved values equal the input.

Resuming after interruption

Read the same IDs again. Preserve correct settings and update only differences.

[blocked]

Confirm identity

Search for existing customers by phone or channel identifier before creating one. Matching names and shared phone numbers can be ambiguous. Have a responsible staff member resolve uncertain matches.

[blocked]

Choose profile fields

Put lasting customer attributes in customer custom fields. Store visit-specific information on the reservation instead. Field keys support queries and connections; distinguish them from display labels.

[blocked]

Create or edit the profile

Enter values in Customers and save. When editing, confirm the organization and customer identifier again. Do not guess channel identifiers or copy them from another customer.

Customer states are lead, qualified, active, churned, and lost. Apply your organization’s lifecycle definitions. Changing a state does not create advertising consent.

[blocked]

Check the saved record

Reopen the customer and check values and organization. Verify that related conversations and reservations still belong to the right customer. Review duplicates and missing identifiers to reduce misdirected follow-up.