Why WebAlf

What should you connect to your website first?

Follow one enquiry or sale to decide what to connect, which details to pass on and how to test the result.

Ask for an order someone remembers

Imagine a bookseller with a shop counter and an online store. In the morning a customer takes home the last copy of a novel. In the afternoon somebody orders the same edition online. A member of staff has to call, offer another edition and cancel the original order. That small incident gives you a starting point for a conversation about integration. You know which event mattered, who noticed the problem and what it cost the customer.

Ask the person who handled the order to walk through it. Where did they see the sale? Where did they check the stock? How did they know the two records referred to the same edition? An anonymised order is enough for this exercise. For a service business, try an enquiry somebody had to copy from an email into the customer relationship management system, or CRM. Pick an example recent enough for the person doing the work to remember the details.

Find the handover that creates extra work

On a sheet of paper, make three columns. Record what a person does, what changes in their software and who needs that information next. The bookseller records the sale at the till. The stock system deducts a copy. Now ask how the online shop hears about it. Perhaps an assistant updates the website by hand. Perhaps a connection already exists but runs at closing time. Those are different problems with different remedies and different costs.

Keep a short log for a typical working week. Note how often the incident happens and how long each correction takes. Record the consequence for the customer separately from the time spent by staff. A rare problem with a paid order can deserve attention before a much more frequent but harmless copy-and-paste task. It is easier for the owner and the developer to agree what comes first when both effects are visible.

Decide who owns each piece of information

Different people may look after different facts about one product. The website editor chooses the cover image and writes the description. The shop manager sets the selling price in the stock system. A cashier records the sale. If two systems can update the same field, establish which value takes precedence. What should happen if the editor corrects a price in the morning and an older price arrives from the accounts system that afternoon?

Also agree how records will be matched. Two editions may share a title, a customer may send several enquiries and different branches may use the same local order number. Show the developer an example where a match is ambiguous. Identify a stable reference that both systems actually hold. Decide what should happen if it is missing. An assistant reviewing a flagged record can be a better outcome than software quietly selecting the first similar title it finds.

Describe one short route from start to finish

For a service business, a sensible first connection might take an enquiry from a form into the CRM. Describe one complete route. A visitor submits the form on the Valencia renovation page. The sales team sees a new enquiry with a phone number, the chosen service and a link to the original page. Agree who receives it and how that person knows they need to reply. The recipient should be able to start the conversation from the record they receive.

Mark where the first release ends. In this example the team can handle the enquiry, while scheduling a visit and calculating a quote are separate pieces of work. Running the first connection gives you a chance to see whether the information collected is useful. If everyone handling an enquiry starts by asking for the floor area, one extra question on the form might do more for the next stage than an automated estimate based on incomplete details.

Discuss the awkward cases before asking for a price

Start with a repeated submission. A customer taps twice on a phone while the first request is processing. Should two enquiries appear? What if the same person comes back an hour later to ask about a different service? Write down both examples. The developer has a way to distinguish a technical repeat from a genuine second request. The person receiving enquiries has a pair of tests they can recognise without reading a technical specification.

Next, imagine a brief interruption. Your website receives the enquiry while the CRM is unavailable. Decide where the request will wait, who can see the queue and how it should be sent once the connection returns. Finally, consider a change to a completed handover. A buyer cancels an order or changes the quantity. Does the stock go back on sale straight away? The answer depends on whether the shop reserved the item, handed it over or has actually received a return.

Ask to see both ends of the connection

Include a future user in the acceptance check. Have them send a test enquiry from a phone, locate it in their CRM queue and process it without a prompt. For a stock connection, choose a particular product and record the quantity before and after the sale. Keep the time, the test reference and the expected result together. If updates run periodically, agree how long to wait before checking and when a delay should be treated as a problem.

Write down what the team actually observed. One new record appeared, it contained the correct service and phone number, and the assigned member of staff saw it among their open enquiries. Repeat the submission and check what changes. The shop equivalent is to sell the last available unit and then try ordering it online. Use test stock or agree a suitable time with the shop before trying a scenario that could affect a real customer.

Bring evidence to the first conversation

Prepare one anonymised enquiry or order, the names of the systems in use and two short lists. In the first, put the details somebody has to transfer by hand. In the second, describe what a customer experiences if the update arrives late or contains an error. Invite the person who will deal with exceptions after launch. They may spot that a branch is closed on Mondays while every unassigned enquiry currently lands in that branch's queue.

Finish the meeting with a sentence you can demonstrate later. A bookseller might choose: once the last copy has been sold at the till and the agreed update interval has passed, customers can no longer order it online. A service team might choose: after a form submission, the assigned person can find one enquiry containing everything they need for the first call. That sentence gives you a manageable first integration and a concrete way to decide when it is ready.