SquidSupport
Product reference / Settings

Basecamp routing

In the app: Settings → Basecamp

Needs the 'View Integrations' permission.

Decides where the AI agent files its Basecamp to-dos. The AI creates a to-do when it needs someone outside the conversation to act, for example a supplier who must cancel or change an order. This page says, per store, supplier and reason, which Basecamp project and to-do list that to-do goes to. The page appears in the Settings menu once Basecamp is connected; the connection itself is made on Settings → Integrations.

Config sets

Needs the 'Edit Integrations' permission.

A config set is a named group of routes plus the stores that use it. One config set can serve several stores, so stores that work with the same suppliers share one set of routes.

The left column lists the config sets, sorted by name. Each shows how many stores and how many routes it has. Click one to open it.

  • Create: type a name in "New config set" and click "Create" or press Enter. The new set is empty: no stores and no routes. Two config sets cannot have the same name.
  • Rename (pencil): change the name in place. Enter or the tick saves; Escape or the cross cancels.
  • Duplicate (copy icon): makes a new set named after the original with "(copy)" added, holding the same routes. Store assignments are not copied, because a store can be in one set only.
  • Delete (bin): asks for confirmation, then removes the set with its routes and its store assignments. This cannot be undone. The stores that used it are left without a config set.

Seeing this page needs the 'View Integrations' permission. Every change on it needs the 'Edit Integrations' permission.

Assigned stores

Needs the 'Edit Integrations' permission.

"Assigned stores" lists every store with a checkbox. Tick a store to make it use the open config set; untick it to take it out. Each change is saved at once and applies to the next to-do the AI files.

A store can be in one config set at a time. A store that already belongs to another set is disabled here and shows "In" followed by that set's name. Untick it there first.

A store that is in no config set has no routes from this page. If it still has routes that were saved for that one store before config sets existed, those keep being used until the store is put in a config set; they cannot be seen or changed here.

Routing

Needs the 'Edit Integrations' permission.

"Routing" holds the routes of the open config set. A route says: for this supplier and this reason, file the to-do in this project and to-do list, assigned to these people.

When Basecamp is not connected, the section says "Connect a Basecamp account before configuring routing." When your Basecamp login has access to more than one Basecamp account, it asks you to choose which account to use, with a link to do so.

A route is added in five steps. Each step appears once the one before it is filled in, and a sentence above the steps reads the route back as you build it.

  1. "Supplier": one supplier, or "All suppliers". An "All suppliers" route is the fallback for orders whose supplier has no route of its own. Suppliers come from Settings → Suppliers.
  2. "Reasons": the kinds of to-do the route is for. Tick one or more: "Cancellation", "Cancellation dispute", "Modification", "Modification dispute", "Tracking", "Tracking dispute", "Incomplete/Failed Delivery", "Incomplete/Failed Delivery (dispute)", "Wrong item sent", "Wrong item sent (dispute)", "Pre-sale" and "Reshipment". Each ticked reason becomes its own route to the same project and list. A reason that already has a route for this supplier is disabled. The AI can also file a to-do for an unauthorized order, but that reason is not in this list, so it cannot be given a route here.
  3. "Project": the Basecamp project the to-do is created in. The list comes from the connected Basecamp account.
  4. "To-do list": the list inside that project. A project without to-do lists offers "Default (No to-do list)".
  5. "Assignees": the people in the project the to-do is assigned to. Search by name, email or company and pick any number, or none. "Notify assignees" is ticked by default; when it is ticked, Basecamp notifies the assignees that the to-do was created.

"Save route" stores one route per ticked reason. Routes are saved one at a time. If a later route fails to save, earlier ones stay saved. Saving also sets up the connection that lets Basecamp report back to Squid about that project's to-dos and comments; you do not have to configure anything in Basecamp.

Saved routes are listed under the steps, each with its supplier or "All suppliers", its reason, and its project and to-do list. The bin button on a route deletes it at once, without asking for confirmation. A route cannot be edited: delete it and add it again.

How a to-do is routed

When the AI files a to-do for an order whose supplier does not receive its tickets through the Supplier Portal, Squid looks at the config set of the conversation's store:

  1. It uses the route for the order's supplier and the to-do's reason, if there is one.
  2. Otherwise it uses the "All suppliers" route for that reason.
  3. A "Reshipment" to-do without a route of its own is filed like a "Modification" to-do.

Only a route of the supplier's own reaches that supplier. A to-do that falls back to the "All suppliers" route goes wherever that route points, so point it at a project your own team watches.

If no route is found, no to-do is created. The AI is told that Basecamp routing is missing for that store, supplier and reason, and to hand the conversation to a person. An unauthorized-order to-do cannot be given a route on this page. It needs a route configured through the API or it cannot be created in Basecamp. A supplier that receives its tickets through the Supplier Portal needs no route.

Changing or deleting a route does not move to-dos that were already created.