Equipment OEMs and EPCs must manage installations, commissioning and long-term service across many customers and regions. Here is how Servy, OpsForms, Hubsource and OpsBot bring order to warranty, AMC and project operations.
| Solution | Role in this use case |
|---|---|
| Servy | Core system of record for assets, customers, contracts, warranties, tickets, technicians, vendors and SLAs. |
| OpsForms | Checklists and forms for installations, commissioning, PM visits, breakdown jobs and audits. |
| Hubsource | Catalog and quoting layer for AMCs, spares and services; approved quotes auto-create Servy jobs. |
| OpsBot | Knowledge layer giving teams and customers answers, SOPs and guided flows; can create or update Servy tickets. |
Assets, serials, customers, locations, contracts and warranties set up in Servy as the master record.
Installations and commissioning executed using OpsForms checklists; once completed and approved, assets go live with full history.
Requests from customers, call center, field app or IoT events create Servy tickets with asset, warranty/AMC and SLA context automatically.
Hubsource holds standard AMC packages, installation bundles and chargeable services. Accepted quotes auto-create Servy jobs and link to revenue.
Technicians and partners use OpsForms during visits; Servy records time, parts, expenses and outcomes for every job.
OpsBot helps internal teams and customers with troubleshooting, FAQs and what-next guidance — can open tickets or track progress.
Leaders see installed base, SLA performance, warranty vs out-of-warranty work, contract revenue and partner performance.
| ❌ Today | ✅ With Starlly |
|---|---|
| Installed base data and warranties scattered across systems with no single view. | Servy holds a clean, central view of assets, warranties and contracts for all customers. |
| Service coordinated via calls, emails and spreadsheets — jobs get lost. | Servy orchestrates all tickets, visits, vendors and costs with clear ownership. |
| Install/commission checklists inconsistent and poorly stored across regions. | OpsForms standardizes them and ties every completed form to the specific asset. |
| AMCs and chargeable services priced inconsistently across teams. | Hubsource defines standard offerings and feeds Servy with clear jobs and prices. |
| Support knowledge scattered in documents and people's heads. | OpsBot makes it searchable and actionable for teams and customers instantly. |
Better recovery on out-of-warranty work and reduced leakage from poor warranty tracking.
Predictable service and better NPS through structured SLA enforcement and escalation.
Consistent, checklist-driven installations and commissioning reduce time-to-live per asset.
Clear revenue and cost view per contract, customer and partner for business decisions.
Standardized flows make onboarding new partners and expanding to new regions much faster.
Customers can access asset status, ticket progress and documentation through a controlled portal.
| Step in the flow | What happens | Solution(s) |
|---|---|---|
| 1. Define offers | AMC, install and service packages defined in Hubsource catalog. | Hubsource |
| 2. Sell & agree | Quotes prepared and accepted; contracts tied to assets in Servy. | Hubsource Servy |
| 3. Install & commission | Technicians follow OpsForms; assets go live with full history attached. | OpsForms Servy |
| 4. Run service | Tickets created with warranty/AMC context; visits executed via OpsForms. | Servy OpsForms |
| 5. Guide & support | OpsBot answers questions, suggests SOPs and opens tickets for teams and customers. | OpsBot |
| 6. Review & grow | Dashboards show SLA, revenue, warranty, partner performance and growth opportunities. | Servy Hubsource |