SquidSupport
Product reference / Supplier Tickets

Supplier ticket

In the app: Supplier Tickets → a ticket

Needs the 'View Supplier Tickets' permission.

One supplier ticket: the request, everything that was said and changed on it, and the controls to answer, reassign and complete it. It opens from the list on Supplier Tickets.

Ticket header

  • "← Supplier Tickets" goes back to the list.
  • "Reference": the first eight characters of the ticket's reference. The search on Supplier Tickets finds the ticket by it.
  • "Copy link" copies the address of this ticket so you can send it to a teammate.
  • "Slack thread ↗" opens the ticket's thread in Slack. It is shown once the ticket has a thread in the supplier's Slack channel, which is linked under Settings → Suppliers.
  • The subject, and under it labels for the status ("Open" or "Completed"), the category, the store and who filed it ("ai", "agent", "system" or "supplier"), the order number when there is one, and "Created" with the time the ticket was made.
  • The request text and the files attached when the ticket was made. A file opens in a new tab.

Two notes can appear under the labels:

  • On a general thread: it has no order and no conversation, the AI never reads it and it never triggers a message to a customer.
  • On a ticket for an internal supplier: comments by that supplier's members count as supplier comments and trigger the AI follow-up, and the ticket is never visible to supplier logins. A member of an internal supplier is a teammate who is assigned to the ticket or is one of that supplier's default assignees.

A teammate whose access is limited to certain stores cannot open a ticket of another store; the page then says the ticket could not be loaded.

Activity

"Activity" is the ticket's history. "Ticket created" comes first, then everything else, oldest first. It mixes comments with changes:

  • "Ticket created", with who filed it ("Squid AI", "System" or "Staff") and where it went: the Supplier Portal, Basecamp or nowhere. A general thread that a supplier started also reads "Staff" here; the name in front of the line is the supplier's user.
  • Comments, each with the name of the writer and a label for staff, the supplier, the AI or the system. Files attached to a comment can be downloaded.
  • Changes: status, priority, due date and supplier, with the old and the new value, and the name of who made the change. A change of assignees shows the new assignees only.

What happened with a comment is shown as a label under it, often followed by the reason:

  • "Customer informed": the AI sent the customer a message about it. "Open reply ↗" opens that message in the Inbox.
  • "No customer message": no message went to the customer. Either the AI read the comment and decided the customer did not need one, or the comment is one the AI does not read. Staff comments carry this label too, with the reason that the comment is not a supplier update.
  • "draft": the AI wrote the customer message as a draft that waits for staff approval in the conversation.
  • "Failed" with the number of attempts so far: the AI could not process the comment. Squid tries again, up to five attempts. After the fifth, look at the customer's conversation yourself.
  • "pending" or "processing": the AI has not finished with the comment yet.

A line marked "Duplicate request" means the AI wanted to file a request that this open ticket already covers, and added the new information here instead of making a second ticket.

"Update customer" appears under every comment written by a teammate on a ticket that is linked to a conversation. A staff comment does not start the AI by itself; this button asks the AI to read that comment and decide whether to message the customer. It needs the 'Manage Supplier Tickets' permission. Clicking it a second time on the same comment does nothing. On a ticket that was made while the Supplier Portal was turned off, the page says the follow-up is queued, but the AI does not run.

Adding a comment

Needs the 'Create Supplier Tickets' permission.

The box under the activity adds a comment.

  • Type @ to mention a teammate or one of the supplier's users. They are notified, also when they are not assigned to the ticket.
  • Attachments: up to 10 files; images, PDF, CSV and XLSX, up to 10 MB each. If the comment is saved but a file fails to upload, the button changes to "Retry uploads" so the comment is not posted twice.
  • "Post comment" adds the comment to the thread, where the supplier sees it in the portal.

Who is notified of a staff comment, in the portal and by email: the supplier's users who are assigned to the ticket. When none of them is assigned, all active users of that supplier are notified. On a ticket for an internal supplier it is the assigned teammates, or the supplier's default assignees when nobody is assigned. The email leaves about a minute later, and several changes within that minute go out as one email. On a ticket made while the Supplier Portal was turned off, only the people you mention are notified.

The comment itself is not sent to the customer. A comment from an internal supplier’s member can start the AI customer follow-up. Posting needs the 'Create Supplier Tickets' permission. Without it, the box is replaced by a "View only" notice. That notice also says you cannot edit, but a person with the 'Manage Supplier Tickets' permission can still edit the details.

Details

Needs the 'Manage Supplier Tickets' permission.

The panel on the right holds the ticket's settings. Changing them needs the 'Manage Supplier Tickets' permission; others see the values greyed out, without "Edit assignees" and "Save details".

  • "Status": "Mark as complete" completes the ticket; on a completed ticket the button reads "✓ Completed · Reopen" and reopens it. The time of completion is shown under it. This button acts at once, and it drops changes in the other fields that you have not saved yet. Completing does not delete anything, and a completed ticket stays in the "Completed" view on Supplier Tickets. Reopening notifies the supplier's side.
  • "Supplier": moves the ticket to another supplier of the same store. The old supplier loses access to the ticket. Supplier users who were assigned are removed, because they belong to the old supplier. The text under the field says the new supplier is notified; in fact only the ticket's assignees are: the teammates on it, and the users of the new supplier that you tick under "Assignees" before saving.
  • "Assignees": "Edit assignees" opens a list of teammates and the supplier's users to tick. The new assignees are notified.
  • "Due date": the date an answer is due. The supplier's side is notified of a new date.
  • "Priority": "Normal" or "Urgent".
  • "Save details" stores changes to the supplier, the assignees, the due date and the priority together. Nothing changes until you click it.

Each change is added to the activity with your name. A change here does not send a message to the customer, with one exception: when a member of an internal supplier completes the ticket, that counts as the supplier completing it, and the AI follow-up runs.

  • "Conversation": "Open conversation ↗" opens the customer's ticket in the Inbox that this request belongs to. A ticket without one shows "None".
  • "Reference": the ticket's reference, the same eight characters as at the top.

AI follow-up

This panel is shown on a ticket that is linked to a customer conversation. On such a ticket, eligible supplier comments and supplier-side completions queue an AI follow-up. Comments can be left without a customer message when the customer conversation was resolved or closed by staff, or when the follow-up was stopped or handed to staff. It decides whether the customer should get a message, for example that their order was cancelled or what the tracking shows. A reply can be sent in that conversation or saved as a draft for staff approval. A daily processing limit can leave updates queued until later. The teammates assigned to the ticket and the teammate who filed it are notified of the supplier's comment either way.

The supplier's side is the supplier's own users, and for an internal supplier its members.

What does not start the AI:

  • a comment written by staff, unless "Update customer" is used on it;
  • a teammate completing the ticket, unless that teammate is a member of an internal supplier;
  • completing tickets with the bulk bar on Supplier Tickets;
  • anything on a general thread;
  • anything on a ticket that was made while the Supplier Portal was turned off in Settings.

The result for each comment is shown in the activity, as described above.