Question 1

Is MIPL Service360 only a help-desk system?

Accepted Answer

No. Help desk is one part of the platform. It also covers product and serial registration, warranty entitlement and claims, field service execution, AMC and preventive maintenance, and dealer service networks in the same system.

Question 2

Can it manage both warranties and service tickets?

Accepted Answer

Yes. A service request can be validated against warranty policies, AMC coverage or a support plan, so entitlement and resolution stay connected to the same record.

Question 3

Can it support field technicians?

Accepted Answer

Yes. Technicians receive assigned jobs with asset history, checklists, parts recording, photograph capture, digital signature and service report generation on mobile.

Question 4

Can it manage AMC and preventive maintenance?

Accepted Answer

Yes. Contracts, coverage, preventive-maintenance schedules, planned visits, reminders and renewal tracking are standard capabilities configured to your contract structure.

Question 5

Can it support dealer and service-centre networks?

Accepted Answer

Yes. Dealer hierarchies, service-centre onboarding, territory mapping, dealer-created claims, approvals, reimbursement tracking and performance scorecards are supported.

Question 6

Can it be used as an internal IT service desk?

Accepted Answer

Yes. The same workflow engine supports internal incidents, employee requests, a service catalogue, approvals, department queues and asset assignment.

Question 7

Is it suitable for government organizations?

Accepted Answer

The platform supports citizen complaint intake, department routing, SLA tracking, escalations, audit history and flexible hosting including in-country data residency, subject to the approved implementation scope. We do not claim compliance with any specific government standard unless it has been verified for your programme.

Question 8

Can it integrate with an ERP?

Accepted Answer

The platform can be integrated through available APIs or agreed data-exchange methods. The final approach depends on the customer's existing system and access.

Question 9

Can it integrate with SAP?

Accepted Answer

Integration with SAP is possible where suitable interfaces, permissions and technical support are available from your SAP team or partner. It is scoped as an integration project rather than a pre-certified connector.

Question 10

Can it integrate with a CRM?

Accepted Answer

Yes, subject to the interfaces the CRM exposes. Typical patterns include customer and contact synchronisation and shared service history references.

Question 11

Can it integrate with inventory systems?

Accepted Answer

Parts availability, consumption and returns can be exchanged with inventory or warehouse systems through APIs, scheduled synchronisation or secure file exchange.

Question 12

Does it support APIs?

Accepted Answer

Yes. REST APIs and webhooks are available for integration-ready implementations.

Question 13

Does it support WhatsApp?

Accepted Answer

WhatsApp messaging requires a customer account with an approved WhatsApp Business provider, approved message templates and implementation configuration.

Question 14

Can it integrate with email and SMS?

Accepted Answer

Yes, using your email infrastructure and an approved SMS provider. Sender identities, templates and delivery rules are configured during implementation.

Question 15

Is cloud deployment available?

Accepted Answer

Yes. MIPL-managed cloud or your own cloud subscription are both supported.

Question 16

Is on-premise deployment available?

Accepted Answer

Yes, where your infrastructure, operating system and database prerequisites are met and maintained by your team.

Question 17

Can data be hosted in the customer's country?

Accepted Answer

Data-residency options depend on the selected deployment model and hosting region agreed in the implementation scope.

Question 18

Does it support role-based access?

Accepted Answer

Yes. Roles determine module access, record visibility and permitted actions, with user administration handled by your nominated administrators.

Question 19

Is audit history available?

Accepted Answer

Yes. Key record changes, status transitions and approvals are recorded in audit history according to the configured scope.

Question 20

How are backups handled?

Accepted Answer

In MIPL-managed cloud, backup planning is agreed as part of the service arrangement. In customer-hosted and on-premise deployments, backup execution remains with your infrastructure team.

Question 21

How long does implementation take?

Accepted Answer

Timelines depend on scope, number of processes, integrations and data migration. We plan implementations in phases and agree the schedule after discovery rather than promising a fixed duration upfront.

Question 22

Can we start with a pilot?

Accepted Answer

Yes. A pilot for one region, product line, dealer group or department is a common starting point before wider rollout.

Question 23

Can the platform be customized?

Accepted Answer

Configuration is used first. Customization is considered where a business requirement cannot be met through configuration, and is agreed as scoped work.

Question 24

Can existing data be migrated?

Accepted Answer

Yes. Customers, products, serial numbers, contracts and open service records can be migrated using structured templates and validation cycles.

Question 25

Is training included?

Accepted Answer

Role-based user training and administrator training are included in the agreed implementation scope.

Question 26

How are requirements gathered?

Accepted Answer

Through structured discovery workshops covering intake channels, entitlement rules, workflows, field operations, reporting and integrations.

Question 27

What support is available after launch?

Accepted Answer

Post-launch support and enhancement arrangements are defined in the support agreement, including issue handling and change requests.

Question 28

How is the product priced?

Accepted Answer

Pricing is prepared after scope discussion. Please contact us for a proposal aligned to your modules, users and deployment model.

Question 29

Is pricing based on users or modules?

Accepted Answer

Both models are used in practice. The commercial structure is confirmed in the proposal based on the selected capabilities and user profile.

Question 30

Are mobile applications included?

Accepted Answer

Mobile field-service usage is part of the field service capability set within the agreed scope.

Question 31

Are integrations charged separately?

Accepted Answer

Integrations are usually scoped and estimated separately because effort depends on the target system and available interfaces.

Question 32

Is annual support required?

Accepted Answer

An annual support arrangement is recommended to cover issue resolution, platform updates and enhancement planning.

Question 33

Can implementation be phased?

Accepted Answer

Yes. Phased implementation by process, region or business unit is our standard recommendation.

Question 34

Does the platform include AI?

Accepted Answer

Advanced AI capabilities are treated as optional or phased items. They require separate validation, data readiness review and approved scope.

Question 35

Can AI classify or summarize tickets?

Accepted Answer

Assisted classification and summarisation can be evaluated as an optional capability. It is not presented as standard functionality.

Question 36

Does it support predictive maintenance?

Accepted Answer

Preventive maintenance based on schedules and usage rules is standard. Predictive maintenance using telemetry or IoT data is an optional, scope-dependent capability.

Question 37

Can it detect duplicate warranty claims?

Accepted Answer

Repeat-claim and duplicate-claim visibility can be configured using serial, customer and date rules. Advanced fraud detection is an optional capability requiring separate scope.

Frequently asked questions

Product scope

Integration

Deployment and security

Implementation

Commercial

AI and advanced features

Still have questions about scope or integration?