Upload more data
Your first dataset came in during registration. This page covers the rhythm afterwards: adding report cards, adding bots, and the rules that apply once you have more than one upload behind you.
The file format never changes. See Prepare your data.
Adding a report card
- On the bot in your bot list, shown on Starter when you are entitled to a new card.
- Inside the bot, above the list of cards it already has.
On Starter the button carries an Upgrade note whenever you are not yet eligible, which means fewer than 30 days have passed since your last upload.
The form is the one you saw at registration, minus the industry field. Attach your CSV and generate. Processing works the same way, and you are emailed when the new card is ready.
How often you can upload
Starter
One card every 30 days, counted from the date you uploaded, not from the period your data covers.
Upload May's conversations on 21 June and your next upload is available on 21 July, whatever months those files describe.
You keep every card you generate. The limit is on how often you create them, not on how many you hold. What Starter does limit is bots: you get one, so everything you upload should come from the same assistant. Conversations from two different assistants mixed into one bot produce a score that describes neither.
Growth and Enterprise
No waiting period, as many bots as you want, and as many cards per bot as you need. The 30-day cap on the period a single dataset may cover is a Starter limit only, so one card can cover a quarter or a year if that suits you.
Naming
Cards are named automatically from the date and time they were generated, for example Astronut 20260521122534. You can rename a card from its own Bot Report Card page, using the pencil icon next to the title.
Do this. A list of timestamps tells you nothing a year later; Q2 2026 or After the June release tells you everything.
Adding a bot
Create one bot per assistant. Use + Add a bot from your bot list.
You choose the industry again, and as at registration it cannot be changed afterwards.
Overlapping periods
Keep your uploads to periods that do not overlap. The system copes with overlap, but the resulting cards will confuse you.
Two things can happen:
The conversations are duplicates. Any session_id already in Inquio is skipped. The new card then begins at the first conversation that was not a duplicate, so its period may not be the one you expected.
The periods overlap but the conversations are new. The card contains only the newly uploaded conversations. It does not fold in conversations from the overlapping stretch that arrived in an earlier upload, so the card describes less than its date range suggests.
In both cases all your data remains visible through Live data. It is the card that becomes misleading, not your dataset.
The order matters if you are also near a size limit: duplicates are removed first, and the conversation limit is applied to what is left, oldest first by timestamp.
Splitting strictly by date causes this more often than anything else, because conversations that cross midnight land in two files.
What appears in your second card
Trends.
A trend compares your card against the immediately preceding interval of the same length. A card covering seven days is compared against the seven days before it; a card covering 35 days against the previous 35. Your first card had nothing behind it to compare against, so the arrows were absent.
From your second upload onward, each Inquio Score dimension carries an arrow showing which way it moved. This is where regular uploading starts paying off: a single card tells you where you stand, and a sequence tells you whether your changes worked.
For the comparison to mean anything, the preceding interval has to be in Inquio. Leave a gap between uploads and the trend has less to measure.
Billing
On Growth you are charged per conversation analyzed. Duplicate conversations that were skipped are not charged.
See Plans and limits.
Deleting
Report cards cannot be deleted. Bots can.
Deleting a bot removes its cards with it, and there is no way to recover them. The confirmation asks you to type the assistant's name first.
A recommended rhythm
One bot per assistant. One card per period, on a fixed cadence: monthly or quarterly, whichever matches how often you actually ship changes.
Consistency matters more than volume. Cards covering equal, adjacent periods give you trends that mean something. Irregular uploads of varying lengths give you a pile of snapshots that are hard to compare.
When you need a view that does not fit the card boundaries, such as a single day or a period spanning two cards, use Live data rather than re-uploading.
API ingestion
On Enterprise plans, Inquio can receive data through the API and generate cards automatically on an agreed cadence: daily, weekly, or monthly. The schedule is set up with your account contact.
Contact sales to arrange it.