When orders arrive from a website, marketplace and conversations, managers spend time finding context. KeyCRM can provide a shared workspace for these enquiries and orders. Connected channels do not by themselves create a coherent process: the team needs rules for identifying new customers, assigning orders and changing their status.
Separate customers, enquiries and orders
One person may send a chat message, place an order and call later. These are not necessarily three new customers. A repeat purchase by that person is nevertheless a new order. Before migration, agree duplicate-matching rules: how phone numbers, email addresses and source identifiers are used, and which cases require manual review.
The official KeyCRM help centre treats orders, buyers, companies and products as related entities. Implementation should reflect that distinction in your working rules. A parcel recipient may differ from the buyer, for example, so their contact details should not automatically be merged.
A source should explain where an order came from
Define how each channel creates orders, which fields it supplies and who checks them. A source explains sales context and helps locate the original record. If the website sends its own order number, keep it in an agreed field. This supports troubleshooting and checking whether the same operation arrived again.
-
Map field names and contact formats for each source.
-
Identify where product codes, prices and stock originate.
-
Agree who sees orders that failed to transfer.
A status should represent a completed action
New, confirmed and dispatched statuses are useful only when transition criteria are clear. Confirmation may require contacting the customer; dispatch may require a booked shipment. If managers interpret the same labels differently, reports will not explain actual progress. Describe cancellation, refused delivery and returns separately.
Learning example: enquiries from two channels
A customer places a website order and then messages to change the delivery address. Test whether the manager can find the correct order, retain its earlier context and make the change without creating another sale. After dispatch, reconcile the address, ordered items and linked delivery document.
When preparing KeyCRM at ALL IT Agency, we turn this scenario into an acceptance test. It checks the source, customer record, manager workflow and delivery integration together. This provides more insight than demonstrating an empty workspace with configured status colours.
What to agree before the team switches
Run a limited pilot with agreed orders. Follow a standard purchase, repeat enquiry and return. Assign owners for reference data and configuration changes. Check channel, automation and permission capabilities in the actual workspace, since product and integration terms can change.
Sources and further reading
