EDDAFOR BUSINESS
All use cases

Dealer-request triage

An AI worker interprets incoming dealer requests, connects them to the dealer and programme records and routes the case through the existing automotive systems.

Automotive

Where the work begins

Dealer requests arrive by email, counter call and vehicle-maker portal, alongside RFQ packets and warranty claims. The workflow reads the relevant dealer, part, programme and policy context before deciding how to execute the work.

The problem

Emails accumulate while staff sort and forward them by hand. The next team still needs to find the customer, vehicle, programme and applicable rules before handling the request.

How the workflow works

Select a stage to see the records it uses, the action it takes and the result.

Records

Incoming request
Email, counter calls, portal cases, RFQ packets and warranty claims supply the work.
Dealer context
Dealer and territory records place the request within the network.
Technical and commercial records
VIN, part, fitment, stock, price tier and lead time provide context where relevant.
Programme and policy rules
Programme terms, warranty policy, approvals and exceptions govern routing and execution.

Stages

Work product

Contextual dealer case

Request
The incoming work remains connected to the dealer and programme.
Relevant records
The receiving workflow has the part, vehicle or commercial context needed for that case.
System result
Routing and case handling operate in the existing dealership, ERP and supplier systems.
Stage 1 of 4

Read the request

Input
Dealer request
Action
The worker interprets the incoming message or case, whatever supported channel it arrived through.
Result
Understood request type and content

Oversight

Clear-rule routing and administration can complete automatically. Approval and policy exceptions reach a person.

What changes for the business

Less manual sorting

The team spends less time classifying and forwarding the dealer inbox.

Faster start on the work

Relevant dealer and programme records accompany the request instead of being rediscovered after handoff.

Explore all workflows