AroFlo Booking Forms

Find a booking and see what it made in AroFlo

5 min read AroFlo booking form

Bookings in the AroFlo Bookings menu lists the bookings made on every form. Click a customer's name or View for the booking's own page. Bookings made on one form are also listed on that form's Bookings tab (see Bookings on one form).

The list

Each row shows Booking Date, Time, Organise later (ticked when the customer found no suitable time), Customer, Address, Service, Form, Status, AroFlo Task and Enquiry Date. A booking made from an auth link carries an Auth link badge.

The Booking Date column reads "Callback requested", "To be arranged" or "No date asked for" where there is no date to show. AroFlo Task shows the task number as AroFlo shows it, such as TASK-12.

Search matches the customer, email, phone, address, service, form, status and AroFlo task. Filter by form appears once the account has more than one form. The list reads the latest 500 bookings and says so under the table.

Status

Status Meaning
Waiting The booking was saved a moment ago and has not been picked up yet.
Sending It is being made in AroFlo.
Sent to AroFlo Everything was made, files included.
Sent, sending files The task is made and the customer's files are on their way.
Sent, files not sent, Sent, files stopped or Sent, files not received The task is in AroFlo but some files did not reach it.
Not sent It failed, or was saved and never picked up for more than two minutes.
Stopped It was being made for more than ten minutes and the run died.
Blocked The customer is on the block list, so nothing was made in AroFlo.

Not sent, Stopped and the file statuses offer Send again.

The booking page

The left side holds what the customer entered. The right side holds what Formpiece made in AroFlo.

  • Booking shows the Status with Send again when it applies, the Form, Service, Booking date and Time, and for a booking with a time the Staff, Team and Schedule. A callback shows Best time to call and Customer's note, and says no schedule was made. A booking with no date says the task was made with no schedule and that a note says so. A booking where no time suited shows the Preferred date.
  • Customer, Site and Task show the answers as the form asked for them, with the Task name, Task type, Priority and any Questions.
  • Attachments lists each file with its size and status: Sent to AroFlo, Not sent, Sending or Waiting. Send files again appears when a task is made and some files didn't reach it.
  • Route details appears for a booking that had drives worked out (see below).
  • Timings and UTM Parameters are Business features. On the Free plan they show a notice.

A booking that failed shows "This booking could not be sent to AroFlo" with the reason, and "Fix it, then send the booking again. Steps already done are not repeated." A booking saved but never picked up says "The booking was saved but the booking function did not start on it. Check that the API can invoke it, then send it again."

A booking from an auth link says what it did to the task, such as "Added a visit to task 1234" or "Moved the visit on task 1234", and the time it replaced.

Step, state and AroFlo record

AroFlo has no way to undo or group the calls a booking makes, so each one is kept on the booking as it is done. A booking that stopped part way carries on from there when it is sent again, and never creates a second task.

The table lists, in order: Client, Contact, Location, Task (or Quote and task), Staff assigned, Schedule, Custom fields, Note and Files. A booking with drives adds Travel, a move link adds Old visit removed, and a form that takes payments adds Invoice and Payment. Office notified is last.

Each step is Done, Not yet or Not used. The AroFlo record column says what was made and shows AroFlo's own id. A client that already existed reads "Existing client matched by {how}", and "and updated" when its details were updated. A booking from an auth link shows "Existing, from the auth link" for the client, location and task, and no contact is made.

Left in place and Old visit left in place mean AroFlo wouldn't let Formpiece delete a schedule. It is still on the calendar, so delete it in AroFlo.

On Payment, a booking says "Not applied to the invoice. Reconcile it against the invoice by hand in AroFlo." The invoice is saved. The card payment is not recorded against it.

Route details

A booking made with dynamic travel times and travel blocks on shows the drive before the visit, and the drive after it when the form counts both ends. Each drive lists its calendar time, the drive minutes and distance, the visit it follows or precedes, where it starts and ends, and the schedule it made in AroFlo. A map draws them. The times and routes are those worked out when the booking was taken and may have changed in AroFlo since.

AroFlo check

Check AroFlo loads the records the booking made and compares them with the booking: Client, Location, Task, Schedule and team, Drives, Notes and Files. Each row says Matches, Missing in AroFlo, Differs, For reference or Not checked, and the summary counts the discrepancies.

The check compares AroFlo as it is now with the booking as it was taken. Records edited, moved or deleted in AroFlo show as differences. Task names, descriptions and notes are only checked for being there, never for what they say. The button is greyed out until something has been made in AroFlo for the booking.

When it goes wrong

"The booking could not be sent again."

The message gives the reason. "The booking API could not be reached." means the call never arrived. Try again in a moment.

Send again made nothing new

The confirmation reads "The booking is being sent to AroFlo. Reload in a moment to see how it went." Click Reload on the booking page.

A booking is Blocked

The customer matched the block list under Workflow Tools. The page names the match. A booking from a blocked customer that was still made in AroFlo says so.

The check says Differs for the schedule

Someone moved or edited the visit in AroFlo after the booking was made.