Every connection has one clear job.
Customer channels bring in the request. Shopkeeper builds the plan. The merchant decides when needed. Shopify completes the work, and the dashboard keeps it reviewable.
Four roles, kept distinct
One request. The right surface at each step.
Customer intake
Instagram, email, chat
Customers ask for help where support is available.
Plan
Shopkeeper
Resolves store context and prepares the supported action.
Merchant control
iMessage
Consequential work arrives with the facts needed to decide.
System of action
Shopify
Eligible order and customer changes happen in the store.
Dashboard · configuration, review, and audit
Connect services, set policies and limits, inspect conversations, and review action history without making the dashboard the only place a merchant can work.
Connect the workflow without blurring the surfaces.
The setup stays understandable because intake, control, execution, and review are described as different responsibilities everywhere they appear.
Bring in the request
Customer channels supply the conversation; they are not merchant approval surfaces.
- Instagram customer messages
- Gmail support intake
- Forwarded support email
- Chat on your store
Keep judgment close
Merchant-control channels carry proposals, questions, approvals, and direction.
- iMessage for phone-native review
- Dashboard manual fallback
- Exact action context attached
- No customer inbox role for iMessage
Complete and review
Shopify remains the system of action while the dashboard preserves the operating record.
- Shopify order and customer context
- Supported Shopify mutations
- Action outcomes and approvers
- Workspace configuration and exports
A connected request still follows the same control model.
- 01
Connect Shopify
Authorize the store that supplies order, customer, product, inventory, and fulfillment context.
- 02
Add intake
Connect Gmail or Instagram, or configure the store's support address to forward into Shopkeeper.
- 03
Choose control
Set the autonomy mode and connect iMessage when phone-native merchant approval is wanted.
- 04
Review the loop
Inspect requests, proposals, decisions, executions, and replies from the dashboard.
Start with Shopify, then add only the surfaces you use.
A workspace needs a Shopify store and its operating rules. Customer channels and iMessage are connected separately so each permission and role stays explicit.
- An eligible Shopify store and organization workspace
- A support address or supported customer-channel account
- Store policies, action permissions, and autonomy mode
- iMessage only when phone-native merchant control is desired
Follow the product story.
The practical questions.
- Is iMessage a customer support inbox?
- No. In this product model, Instagram, Gmail, forwarded email, and chat on your store are customer-intake surfaces. iMessage is for the merchant to review, approve, and direct Shopkeeper.
- Is Shopify required?
- Yes. Shopkeeper is built for Shopify stores, and Shopify supplies the commerce context and system of action behind supported order work.
- Can I use forwarded support email instead of Gmail?
- Yes. A store can forward a support address into the provided intake path. The setup should explain the forwarding destination and verification steps without asking customers to change how they write in.
- Does Shopkeeper merge every customer across channels?
- No. It uses the conversation, customer, and Shopify context available to the request. It does not promise perfect cross-channel identity resolution.
- Are TikTok Shop and WhatsApp part of the primary integration story?
- Not for this refresh. They may become separate priorities, but the core story here is Shopify execution, Instagram and email intake, iMessage merchant control, and dashboard review.