SquidSupport
Product reference / Settings

Cost settings

In the app: Settings → Costs

Needs the 'View customer service costs' permission.

What customer service costs your organization: the cost of goods, what your staff cost per hour, the hours they worked and what you pay for tools. Reports → CS economics uses these values for cost per order and margin impact. The values are set once for the organization; only the standard COGS % can differ per store.

Who can use this page

The page exists only for organizations that have Squid Agent switched on, because the report it feeds comes with Squid Agent. Without it, "Costs" is not in the Settings menu, and opening the page shows "Available with Squid Agent" with a "Back to Settings" link. Nothing is loaded or saved in that state.

Seeing the page needs the 'View customer service costs' permission. Without it the page says "Costs need the View customer service costs permission". Changing anything needs the 'Edit customer service costs' permission; without it every field and button is disabled.

Two more limits apply inside the page:

  • Per-person rates are shown to, and can only be set by, the Owner of the organization.
  • A teammate whose access is limited to certain stores sees only those stores under "Standard COGS %" and sees no worked hours. They can change the COGS override of their own stores. They cannot change anything that applies to the whole organization: the "All stores" COGS %, hourly rates, tool costs, the repeat contact window, voucher redemption, productive hours, or worked hours.

Standard COGS %

Needs the 'Edit customer service costs' permission.

One percentage for the cost of goods, not a cost per product. Squid uses it to price replacements and reships and to work out gross margin.

  • "All stores" is the percentage for every store. It can be 0 up to, but not including, 100, with two decimals. Empty means not set; margin then shows "Set your standard COGS % first" and is never treated as zero.
  • "Store overrides" is folded by default. Open it to give a store its own percentage, in the field named after the store with "(override)". An empty override means the store uses the "All stores" value. The fold's title says how many stores are overridden.
  • "Applies from" is the date the new values count from. It starts at today's date in UTC.

"Save" sends only the values you changed, and is available once something changed. The line next to it shows which version last set the COGS %, or "Not set yet".

Staff cost

Needs the 'Edit customer service costs' permission.

The hourly cost of your staff, including overhead. Staff cost in the report is the worked hours you upload multiplied by the rate that applied on each day. Hours uploaded for a person use that person's rate when there is one, otherwise the rate of the team named on that hours row; for everyone but the Owner the report uses team rates only. Hours with no rate at all are not costed. Squid never estimates staff cost from handling time: until worked hours are uploaded the section shows "Staff cost: not set." with an "Upload worked hours" button, and cost per order and margin leave labour out.

  • Team rates: one field per department, labelled with the department's name and the currency per hour. Empty means no rate. A rate can be 0 to 100,000. Departments are created under Settings → Departments; with none, the section says there are no teams yet. Its text points to "Settings → Teams", by which it means Settings → Departments.
  • "Per-person rates", marked "Owner only": one field per person who has a personal rate or appears in the recent worked-hours rows loaded by the page. Only the latest 500 hours rows are loaded, so an upload by email may not make every person appear here. Only the Owner sees and sets these, because they make the cost of one employee visible. Everyone else sees a line saying rates are per team.
  • "Applies from": the date the changed rates count from.

"Save rates" saves the rates you changed. Rates are in your organization's reporting currency unless a rate was stored in another currency.

Worked hours

Needs the 'Edit customer service costs' permission.

Worked hours are uploaded as a CSV file. The table shows recent months through today, rather than all uploaded history, with each month's total "Hours", the number of "Teams" and "People" in it, and who last saved it and when. Hours are kept per team, not per store, so only people who can see every store see them.

The file. The first line is a header with a date column, an hours column, and a team column, an email column or both. Each following line is one day: the date written like 2026-10-31, the department's name or a teammate's email address, and the hours. Example: 2026-10-01,Support NL,38.5.

  • A team name must match a department's name, and an email must belong to a team member. Upper and lower case do not matter.
  • Each row can hold at most 24 hours when it names a person, or 12,000 when it names only a team. These limits apply per row, not to the combined hours for that person across teams. The same day, team and person combination cannot appear twice in a file. Hours may be written with a decimal point or a decimal comma; quote a value containing a comma so it stays in one CSV cell.
  • A file can be at most 1 MB and 20,000 lines.
  • A file is imported whole or not at all. If any line is wrong, nothing is imported and the page lists the problems by line number, up to 50 of them.

"Upload worked hours (CSV)" adds the file. A line with the same day, team and person combination as an existing row replaces that row; other days are left alone.

"Replace this month's upload" appears once there are hours in the displayed period. It first removes every earlier CSV upload between the first and the last date in the file you pick, then imports the file. The range comes from the file, not from the calendar month, so a file covering two months replaces both. Hours that were not uploaded by CSV are kept, unless the file has a line with the same day, team and person combination.

After an upload the page says how many rows and hours were imported, for which dates, and how many earlier rows were replaced.

Monthly tool costs

Needs the 'Edit customer service costs' permission.

What you pay per month for tools. The report spreads each amount over the days of the month and counts it in its AI and tools line.

  • "Add a tool" adds an empty row. Give it a name, up to 120 characters, and an amount in "Per month", from 0 to 10,000,000. A row without a name is not saved.
  • A saved tool's name can no longer be changed; only its amount can. Clearing the amount removes the tool's cost from the "Applies from" date on.
  • The text at the end of a row shows the amount currently stored, or "New" for a row that is not saved yet.
  • "Squid plan": for people who also hold the 'Billing' permission, Squid proposes a row with your Squid plan and its list price; an organization on the free plan gets none. It is a suggestion and only counts once saved. Because the row is already filled in, the next "Save tool costs" saves it together with your other changes; clear its amount first if you do not want it.
  • "Applies from": the date the changed amounts count from.

"Save tool costs" saves the rows you changed. At most 50 tools can be saved at once.

Repeat contact, vouchers and capacity

Needs the 'Edit customer service costs' permission.

  • "Count a new conversation as a repeat contact within (days)": how long Squid watches a closed conversation for the customer coming back. A whole number from 1 to 30. Until you set it, Squid uses 7 days.
  • "Voucher redemption %": the share of vouchers customers actually spend, 0 to 100. Vouchers count at that share of their face value. Empty means not set, so vouchers count at their full face value.
  • "Productive hours per person per day (for forecasts)": how many hours of a working day a person spends on tickets. From 1 to 16. Empty means Squid's default of 6.5 hours is used.
  • "Applies from": the date the changes count from.

"Save" is disabled while the repeat-contact days or productive hours are outside their ranges. An out-of-range voucher percentage does not disable it; saving is refused.

How a repeat contact is counted. The days are counted from when the earlier conversation was closed, not from when it was opened. Conversations belong to the report period of their first recorded close. Conversations closed before close history began use their stored close date. If they reopened before their first recorded close, their original close is unknown and they are left out. A closed conversation counts as repeat-contacted when all of this is true:

  • the same customer starts a new conversation with the same store after that close and within the set number of days;
  • the new conversation is one that counts in reports;
  • the new conversation is about the same thing: the two share an order, or, when they share no order, they have the same first contact reason. When one of the two has neither an order nor a contact reason, the same customer is enough.

For a conversation that was reopened and closed again, Squid looks for the new conversation after its latest close. A conversation that is open again when the report is made has no repeat contact counted.

What is and is not counted:

  • Only conversations that were closed and answered by the AI or by a person are measured. A new conversation with another of your stores does not count.
  • A customer replying in the same conversation and reopening it is not a repeat contact. It does count against first contact resolution when it happens within the same number of days.
  • A close is only measured once the full number of days has passed since the conversation was first closed. Closes from the last few days are left out until then, and the report says how many are not measured yet.
  • A report uses the number of days that applies on the last day of the period it shows.
  • Repeat contact is not worked out for a report period longer than 92 days.

Scheduled changes and history

Every save on this page creates a new numbered version with its "Applies from" date. Nothing is edited in place: reports use the value that was in force on each day, so a change does not rewrite earlier periods unless you date it in the past. The date can be any day from the year 2000 up to one year ahead. Saving values that already apply from that date is refused.

  • "Scheduled" lists up to 50 versions whose date is still in the future, newest version first, or "No changes scheduled."
  • "History" lists up to 50 versions that are in force or were, newest version first: its number, who set it, the date it applies from, and each value it changed. A version that came from an approved Squid Agent proposal says so. Changes to per-person rates are hidden from everyone but the Owner. A store-restricted viewer also has changes for other stores hidden. The version shows a count of hidden changes; its text calls them changes only the Owner can see, even when store access is the reason.

To undo a change, save the old value again with the date it should apply from.