Customer and contacts
Keep company, contact, address, communication and relationship information in a shared customer record.
RastCRM brings customer, sales and field service work into one web and mobile system. Sales teams follow customers, opportunities and quotations; technical teams manage work orders, installations, maintenance and service records.
Sales and service
The sales and service sides can be used together or scoped according to the team that will start first.
Keep company, contact, address, communication and relationship information in a shared customer record.
Follow the sales stage, expected value, product or service lines, quotation versions and related activities.
Sales teams can review customer information, record visits and update the opportunity from the mobile application.
Create installation, maintenance or service work; assign it to the relevant team and follow its status from the office.
Technicians receive assigned jobs, review service history and record forms, notes, photographs and signatures in the field.
Warehouse and field stock movements can be connected to sales or service records where the operation requires it.
Technical structure
The web interface and backend API separate screen logic from customer, sales and service rules.
Dedicated mobile flows are available for technicians, warehouse users and field teams on iOS and Android.
ERP, accounting, payment, messaging or other company systems can exchange the data required by the agreed workflow.
Related pages
Common questions
Customer and contact records, opportunities, quotations, activities and field updates can be managed in the same sales flow. The fields, stages and permissions are configured according to the company’s actual sales process.
Yes. Work orders, installation and maintenance jobs, technician assignment, service forms and equipment history can run alongside customer data. Technicians use the mobile app while the office team follows the operation on the web.
The workflows that need field continuity can keep selected data and pending actions on the device. Synchronization rules are planned according to the data source and the action being completed.
Yes, when the other system provides a suitable integration method. Customer, product, stock, invoice or service data can be exchanged through APIs or an integration service designed for the project.
If Dynamics 365 will remain the central CRM, a custom mobile or web application can be built on top of Dataverse instead of introducing another CRM. We review both options before recommending a structure.
Tell us about the current workflow and systems; we can show the relevant parts in a demo.