Match
01Conversation starts
Customer context is matched to a known record when available.
Customer context
Attach customer records to support decisions.
CRM context gives Replofy account state, lifecycle, ownership, and customer history so support, success, and sales work from the same record.
Conversation startsRecord informs replyAction preparedHuman approves
Customer record
customer history
business context
CRM customer profile
update preview
Profile
Account
Acme Demo
active customer
Segment
Growth
CRM field
Health
watch
3 tickets this week
Previous tickets
REP-1730
Shipping status
resolved
REP-1794
Invoice copy
resolved
REP-1842
Current order delay
open
Write preview
Field
last_support_issue
current ticket
Task
CSM follow-up
approval needed
Audit
CRM write not sent
operator review
context01
Read context
CRM profile and prior support history sit next to the thread.
draft02
Preview update
Aura prepares field changes without committing them.
control03
Approve
Operators decide what gets written back.
Integrations overview
CRM
CRM context gives Replofy account state, lifecycle, ownership, and customer history so support, success, and sales work from the same record.
How it works
customer history
01
Conversation starts
Customer context is matched to a known record when available.
02
Record informs reply
Plan, lifecycle, owner, and history shape the workflow.
03
Action prepared
Aura can prepare a note, task, or handoff.
04
Human approves
Operators decide whether the CRM update should be written.
Data entering Replofy
What CRM contributes.
Data
Used by Aura
Operator control
Data
Customer profile
Used by Aura
Summarize context
Operator control
Verify before action
Data
Lifecycle stage
Used by Aura
Route support or sales
Operator control
Assign owner
Data
Account owner
Used by Aura
Prepare handoff
Operator control
Update task state
Data
Prior notes
Used by Aura
Avoid repeated questions
Operator control
Review relevance
CRM workflow
Support context to customer record.
Context
02Record informs reply
Plan, lifecycle, owner, and history shape the workflow.
Prepare
03Action prepared
Aura can prepare a note, task, or handoff.
Control
04Human approves
Operators decide whether the CRM update should be written.
Guardrails
CRM integration rules.
01
Do not overwrite customer records automatically
02
Restrict sales notes by role
03
Log prepared updates
04
Keep support and sales ownership visible
Related pages
See what to read next.
Integrations
Gmail
Gmail threads enter Replofy with routing, summaries, ownership, AI drafts, approved-source replies, and human send control.
Integrations
Shopify
Shopify data helps Replofy answer order, return, fulfillment, and exchange questions while keeping refunds and exceptions under approval.
Solutions
Sales Pipeline
Replofy preserves customer context, support history, intent, and next action when a conversation should move from support to sales or success.
Review CRM flow
Connect customer records to every conversation.
Give operators context and prepare CRM updates with review.