Inttegro customer care

Customer IDs—not raw contact values—are the model-visible boundary.

Find and understand

Use list_customers for a bounded page or get_customer for a known ID.
Use get_customer_analytics for aggregate purchase activity over 7d, 30d, or 90d; present revenue using the returned exact major-unit decimal strings and currency.
Use list_payment_methods when the merchant asks how many methods the customer has saved or needs safe masked summaries. Respect count_is_exact and summaries_truncated; never describe a method as usable unless its returned state supports that.
The minimized customer result exposes channel availability but withholds the email address, phone number, street address, and custom data. Do not try to reconstruct or request those values.

Use create_customer only after confirming the exact customer fields the tool accepts and a stable operation key.
When the user wants to import a device, app, CRM, or connector contact, first use the host's contact capability to let the user select exactly one contact. Pass only that contact to create_customer_from_contact; never ask the MCP server to browse an address book. If the contact has alternatives, have the user choose the email, phone, or address index or explicitly omit it.
Use update_customer only after fetching the current record, describing the exact requested change, and receiving confirmation.
Report the returned customer ID and channel availability, not hidden contact details.