The follow-up layer
for overseas sales
Meet Iris, your AI sales and service agent.
Multilingual conversations, product answers and support follow-through.
Iris · Workspace with inbox, conversation and AI pre-sales panel
Iris is presented as an independent product under development. Website v1.0 does not offer online chat. Contact us by email to discuss a demonstration; external channels and any Ops ticket bridge require separate configuration and acceptance.
“One question can take five hand-offs: the customer asks, sales looks it up, asks pre-sales, waits, translates, and the customer asks again.”
Who Iris is here forIllustrative workflow, not a customer testimonialSix capabilities,
one customer loop
Independent development scope; optional integration requires separate acceptance.
- WEB SCREENSHOT · I2
Iris · Unified inbox across accounts
A channel-based workspace
The development workspace organizes channel accounts, conversations, owners and status. WhatsApp, email and other external connectors need separate setup, provider approval where required and acceptance.
- WEB SCREENSHOT · I3
Iris · Original and translation side by side
Two-way language assist
Customers write in their own language. Sales reply in Chinese. Iris translates both ways and keeps the original in view.
- WEB SCREENSHOT · I4
Iris · AI pre-sales assistant
A pre-sales assistant for every rep
Looks up product material, asks for missing requirements and drafts a first recommendation. Complex questions go to pre-sales with full context.
- WEB SCREENSHOT · I5
Iris · Website chat guiding a visitor
Website chat that qualifies
A website-channel workflow can collect a question and prepare a draft for staff review. This website has no live Iris consultation; dealer routing is not an accepted capability here.
- WEB SCREENSHOT · I6
Iris · Case progress
After-sales that follows through
The workspace includes enquiry and after-sales workflows. A saved intake is not an Ops ticket, and saving a reply is not proof of external delivery.
- WEB SCREENSHOT · I7
Iris · Customer context and knowledge
Context that stays
Conversation history and knowledge workflows provide context within their configured scope. Cross-product knowledge sharing and automatic publication are not promised.
From inquiry to insight
Each step leaves something the next step can use
Capture- For a configured and accepted channel, retain the incoming message for the team.
External delivery and automatic replies require their own validation. Understand- Use case, region, product conditions and existing equipment are collected.
Leaves: a clear requirement with open items. Propose- Material is found and a first combination drafted.
Leaves: a grounded suggestion, with items for expert review. Convert- Staff confirm the next step and any dealer introduction.
No automatic dealer network or conversion result is promised. Support- Collect material and track an Iris intake.
Ops tickets and customer-facing return messages require a separately accepted connection. Learn- Issues reviewed, good answers approved, product feedback organized.
Leaves: updated knowledge and a list of improvements.
You decide what AI handles
Reception scope, knowledge and handoff depend on configuration and permissions. Human takeover and stale-task behaviour require end-to-end acceptance.
Human-led- For key accounts, complex negotiations and special cases. People reply; Iris looks things up on request.
AI-assisted- For everyday sales and service that need a human check. Iris drafts summaries, suggestions and replies; people approve.
AI-hosted- For repetitive questions with good material and clear rules. Iris replies within its scope and hands exceptions to people.
Iris, an independent workspace
Discuss a demonstration around specific enquiry workflows
Enquiry workflows- Identify the reception, product-information and follow-up tasks your team wants to improve.
Product material- Organize the product information and knowledge needed for those workflows.
Scope discussion- Contact us by email to discuss a demonstration and project requirements.
What a pilot can measure
Measurement topics for a pilot; no measured productivity gains are claimed
Reply to an inquiry- Measure preparation and checking time against an agreed baseline.
Clarify a configuration- Measure the completeness and effort of a pre-sales handoff.
Cover while traveling- Measure after-sales handoff effort, including human review.
Deployment
Choose where the workspace runs, separately from how much AI handles
Your cloud- You own the cloud account and resources. We provide the agreed software, implementation and application services; infrastructure upkeep can be contracted separately.
Dedicated hosting- We run a dedicated environment for you, and your team focuses on knowledge, business rules and results.
AI sales & service questions
AI Sales & Service
Does the sales and service workspace require Energy Management?
Iris is introduced as an independent product. Contact us by email to discuss specific workflows and demonstration scope.
Which channels does the workspace support?
External channels require connector configuration, provider permissions and project acceptance. Their formal commercial availability has not been established by the website tests; website v1.0 uses email contact.
Will AI-hosted replies make commitments on price?
No. Prices, technical conclusions and commitments follow your rules and are confirmed by authorized staff.
How is the workspace deployed?
In your own cloud, or in a dedicated environment we host and maintain.