---
title: "Import summary and billing polish"
description: "The import summary now reports how many contacts were actually added, and billing errors explain themselves instead of failing silently."
canonical: "https://firstsales.io/changelog/import-summary-billing-polish/"
---

1. [Home](/)
2. [Changelog](/changelog/)
3. Import summary and billing polish

[All updates](/changelog/)

FixJune 1, 20262 min read

# Import summary and billing polish

The import summary now reports how many contacts were actually added, and billing errors explain themselves instead of failing silently.

Three small friction points removed from import and billing. None of them are dramatic features — but each one is the kind of thing that catches you off guard at the worst moment, usually when you're trying to move fast and the number you see doesn't match what you expected.

## Small fixes that matter

Fix

Import summary and billing polish

Billing overview with credit balance and runway

## What changed

### Import summary now shows contacts added

When you import a list, the summary screen previously reported how many contacts were _processed_ — which sounds useful until you realize it includes duplicates, skipped rows, and records that didn't actually make it into your list. The number you actually care about is how many new contacts were added and are ready to receive campaign email. Those are very different figures when your import includes rows that already exist in your account or fail validation.

The summary now shows the contacts-added figure directly, so you can confirm a list grew by the amount you expected without doing mental arithmetic or cross-referencing against the contacts table. When a campaign depends on a specific list size, knowing the real number at import time prevents surprises later — like launching a campaign and finding it has half the audience you planned for.

### Billing errors explain themselves

If you don't have permission for a billing action — adding a payment method, adjusting a plan, managing credits — you previously got a generic error with no indication of what went wrong or who could fix it. That error now carries a plain-language message describing the permission gap, so you know immediately whether to adjust your own settings or loop in the workspace owner.

For small teams where billing permissions aren't always obvious, the difference between a confusing dead end and a clear next step saves real time. You stop assuming something is broken when it's actually a permissions question, and the person who can fix it gets involved right away rather than after a round of troubleshooting.

### Credit top-ups start at the payment provider minimum

Credit top-ups now enforce a minimum amount that matches the payment provider's floor. Previously, it was possible to enter a smaller amount that would fail at checkout — completing the form, hitting confirm, and then discovering nothing happened. The floor is now enforced at the point of entry, so the top-up you submit is one that will actually go through. This matters most when you're topping up before a large send and can't afford to discover a failed transaction after the fact.

## Where to look

Your **Billing** page now shows credit balance and runway side by side, so you can tell at a glance whether your credits will last until renewal. The goal with all three fixes is the same: the number you read is the number you can act on, without a second-guessing step in between.

[ PreviousSettings, reorganized](/changelog/settings-redesign/)[Next Campaign logs show pending retries](/changelog/campaign-logs-pending-retries/)