Customer Account Onboarding Agent
Set up new customer accounts across your systems without entering details twice.
When a new customer request arrives, your Trelium agent checks the required information, catches missing or duplicate records, and prepares customer accounts in Shopify and your ERP for review or creation under your existing rules.
Works with the tools your team already uses
NetSuitePreview · full demo coming soon
Where it starts
Start from the request and the rules you already have
- 01
A new-customer request
An intake email, an account setup form, or another trigger your team approves. The agent reads the message and its attachments.
- 02
Your customer setup rules
Your SOP defines which fields are required, who approves a new account, and how tax, credit, and payment details are handled.
- 03
Shopify and your ERP
The customer records the agent creates, and the existing accounts it searches before creating anything new.
Illustrative example
One setup request, one structured customer record
Here is what the agent reads, and what it hands your team before any account is created.
The request · Email
- From
- Maya Chen · Harbor Point Supply
- Subject
- New account setup
Hi team, we'd like to open an account before our first order. Our details are on the attached form. Please ship to our Tacoma warehouse, not the Portland office.
Attachment: new-account-form.pdf
Customer record, ready for review
- Business name
- Harbor Point Supply
- Primary contact
- Maya Chen · maya@harborpointsupply.com
- Phone
- +1 (503) 555-0142
- Billing address
- 1200 NW Front Ave, Portland, OR 97209
- Shipping address
- Needs review: the email asks to ship to Tacoma, but the form only lists the Portland address
- Existing accounts
- No match in Shopify or the ERP by email, domain, or name
- Payment terms
- Not provided. Left for your team to set under your SOP
No records created yet. The agent drafted an email asking for the Tacoma address. Once it's confirmed and the account is approved, the agent creates the customer in Shopify and the ERP and sends both account IDs.
Illustrative example. Harbor Point Supply is a fictional company. Required fields, matching rules, and approval steps follow your team's own SOP.
The impact
New customer details are entered once, checked, and set up the same way in Shopify and your ERP.
The workflow
How it works, step by step
How does the Customer Account Onboarding Agent turn a new-customer request into accounts in Shopify and your ERP? It validates first, checks for an existing customer, waits for any approval your process requires, and only then creates records.
- 01
Reads the request
Reads the intake email or form and its attachments, and pulls out the business and contact names, email, phone, and billing and shipping addresses. Tax or payment details are captured only when they're provided and your SOP asks for them.
- 02
Validates the details
Maps each value to the matching Shopify and ERP fields, normalizes formats like phone numbers and addresses, and checks that every required field is present and consistent. Missing values are never guessed.
- 03
Checks for existing accounts
Searches Shopify and the ERP using the identifiers you approve, such as business name, email, domain, or customer ID. Likely matches are escalated, never merged or overwritten.
- 04
Routes exceptions and approvals
Prepares a review item for your team, or a draft email asking the customer for missing information. If your SOP requires an approval, nothing is created until it's given.
- 05
Creates the records in order
Creates the customer in Shopify and in the ERP in the order your process defines, following each system's rules. Each new account ID is recorded and cross-referenced where the systems support it.
- 06
Verifies and reports
Confirms each record exists, then sends a short summary with links and IDs. If one system succeeds and the other fails, the agent retries safely or gives your team a recovery step, without creating the first record again.
Before and after
From retyping customer details to reviewing exceptions
Your team keeps working in Shopify and your ERP. What changes is who reads, retypes, and double-checks the details.
Before
- 01
Someone reads the new-customer email and opens the attachments.
- 02
They check the required fields by hand and email the customer about anything missing.
- 03
They search Shopify and the ERP to see whether the customer already exists.
- 04
They type the details into Shopify, then type them again into the ERP.
- 05
They go back to confirm both accounts were created and match.
With the agent
- 01
The agent extracts the customer details from the email and attachments.
- 02
Required fields, formats, and conflicting values are checked against your SOP.
- 03
Shopify and the ERP are searched for an existing customer before anything is created.
- 04
Validated, approved requests become customer records in both systems, with both IDs recorded.
- 05
Your team gets a completion summary, or an exception with the exact question to resolve.
Human review
What a person reviews before an account is created
The agent doesn't create records from incomplete, conflicting, or unapproved information. Each of these goes to your team with the original request and what the agent found.
Missing or conflicting details
A required field is blank, or the email and the attached form disagree. The request is held, and the agent drafts the follow-up question for the customer.
Possible duplicate accounts
An existing Shopify customer or ERP account shares a name, email, or domain. The agent shows the likely match and never merges or overwrites an account without approval.
Tax, credit, and payment terms
Sensitive fields follow your SOP. The agent records only what the customer provided, and a person reviews these values before they're set.
System or sync failures
If a system rejects a record or a connection fails, the agent reports what succeeded, what didn't, and the safe next step, instead of creating a record twice.
Key takeaways
Safeguards built into every setup
Each request is processed once: Requests are tracked, so a forwarded email or a repeated form submission doesn't create a second account.
Your systems stay in place: Records are created in the Shopify store and ERP you already run, with the access you authorize. There's no data migration and no ERP replacement.
A clear record of each setup: Every summary links the source request, the checks run, the approvals given, and the account IDs created.
FAQ
Questions about customer account onboarding
The Customer Account Onboarding Agent reads the intake email and its attachments, extracts the customer's business name, contacts, and addresses, and checks them against the fields your setup process requires. Once the request is complete and any required approval is given, it creates the customer records in your systems. Incomplete or conflicting requests are held for review instead.
The agent maps one set of validated customer details to the fields each system expects, then creates the Shopify customer and the ERP customer account in the order your process defines. It records both account IDs and cross-references them where the systems support it, so nobody types the same details twice.
Before creating anything, the agent searches Shopify and your ERP using identifiers you approve, such as business name, email, domain, or customer ID. Likely matches go to a person for a decision. The agent also tracks each request, so the same email or form isn't processed twice, and it never merges accounts without approval.
Yes. The agent checks that every field your SOP marks as required is present, normalizes formats such as phone numbers and addresses, and flags values that conflict between the email and the attached form. It doesn't guess missing values. It drafts the follow-up question instead.
The agent works inside the Shopify store and ERP you already use, with the access you authorize. It doesn't migrate your data or replace either system. It takes over the reading, checking, and data entry your team does by hand today, and follows your existing approval rules.
Your customer setup SOP decides. Before the agent creates any records, we confirm which fields are required, which identifiers count as a match, and which values need approval. Sensitive fields such as tax status, credit limits, and payment terms are set only when your SOP allows it, after a person reviews them.
The Company Store to ERP Sync Agent turns company store orders into ERP sales orders. The Customer Account Onboarding Agent handles customer setup: creating the new customer's account in Shopify and your ERP, before or outside of any order. The two can run one after the other.
Trelium connects to Shopify, to ERPs such as NetSuite and Odoo, and to email tools like Gmail and Outlook. We confirm your specific systems, fields, and setup rules before the agent creates any records.
Related use cases
Related agents and integrations
See it on your workflow
Show us how your team sets up a new customer.
Book a short demo and bring your customer setup SOP or a recent intake email. We'll walk through how the agent would check it, find existing accounts, and prepare the records in Shopify and your ERP.