CRM & Contacts

CRM & Contacts

RevMozi keeps the contact record focused on what changed, what was bought, and what should happen next.

What lives in a contact record

• Lifecycle state derived from events, not manual pipeline updates
• Active and completed enrollments
• Revenue and activity history
• Feedback, testimonials, and operator review status

Request Feedback

When a customer completes an offer, you can generate a feedback link directly from the contact view.

1. Open the contact.
2. Choose the completed enrollment or offer you want feedback on.
3. Click Request Feedback.
4. Share the generated link by email, SMS, or WhatsApp.

RevMozi creates a single-use link that opens the feedback page on the deployed funnel domain. If the token is valid, the page greets the customer and asks for a rating tied to that offer.

What gets captured

• Star rating
• Public testimonial for positive feedback
• Private improvement note for lower ratings
• Display consent for public use
• Customer display name for approved testimonials

Review inside CRM

Submitted feedback appears on the contact record so the operator can review it in context.

• pending: newly submitted and waiting for review
• approved: approved for public reuse
• rejected: kept in CRM but not used publicly

Bulk Import Contacts

Use bulk import when you are moving an existing contact list into RevMozi.

1. Upload the raw .csv or .xlsx file.
2. RevMozi stores the raw file and has the agent inspect headers and small samples instead of pushing the whole file into model context.
3. The agent writes a Python transform that converts the source file into RevMozi's standardized contact CSV.
4. RevMozi stages the standardized file, validates it, and then runs the reliable importer that handles retries, idempotency, and duplicate rules.

Recommended limits:

• Keep each upload under roughly 25,000 rows.
• Split larger datasets into multiple uploads instead of sending one very large file.

Duplicate handling:

• update merges incoming data into matching contacts.
• skip leaves matching contacts untouched.
• Contacts still need at least one identity field: email or phone.

Related docs

• Playbooks
• Feedback Collection release note