What shipped: August 2026
Fifty changes went out in August. The big one is phone number porting, so you can bring your existing number instead of learning a new one. Facebook ad publishing went live after Meta approved our permissions. Bulk tagging got usable. And a long tail of fixes for chat commands that did the wrong thing.
Bring your own phone number
The single largest piece of work in August, at roughly eighteen separate changes, was number porting.
The problem was simple and annoying. Closr gives you a phone number for calls and texts. But you already have a number. It is on your signs, your cards, and in the phone of every client you have ever worked with. Asking you to abandon it is asking you to abandon your database.
So now you can bring it.
I want to port my existing number to Closr
Or go to Settings, then Phone.
The wizard collects the number, validates it is portable, takes your carrier account details and PIN, and asks for a recent bill. It generates the letter of authorization as a PDF for you to sign in the app.
Port request submitted
Number validated, LOA signed, bill attached
Porting is not instant. Once you submit, the carriers talk to each other, and that takes days to weeks. Nothing we build changes that. What we can do is stop you from waiting on a request that was never going to succeed, which is why validation happens before submission instead of after.
Your old Closr number does not vanish the moment the port lands. It is released on a nightly job after the new number is confirmed adopted, so there is no window where you have neither.
Facebook ad publishing went live
Meta approved ads_management and the pages permissions in August. Before that, Closr could
build an ad and stop. Now it publishes.
This one is worth being precise about, because the approval and the capability are different things. We had the ad composer working for months. What we did not have was Meta's permission to push the finished ad to your account. That is a review process, it runs on Meta's schedule, and no amount of engineering shortens it.
Ad reading is still not approved. We asked for ads_read and did not get it in this round, so
performance reporting inside Closr is not there yet. You can publish from Closr and read
results in Meta's own tools.
Bulk tagging that actually scales
Tagging worked in August only if you were patient. You could tag contacts one at a time.
Three changes fixed that:
- Select all matching. Filter the directory, then tag the entire result set, not just the page you can see.
- Tag at import. Apply tags during a CSV import, so contacts arrive already sorted instead of needing a second pass.
- Chat bulk tagging. Hand the assistant a list of emails or ids and it tags them, capped at 500 per request.
Tag everyone from the Oakville open house as open-house-oct
- Cap, not truncation
When a bulk request goes over the 500 limit, Closr refuses the whole thing and tells you. It does not silently tag the first 500 and drop the rest. A partial write you do not know about is worse than a failure you do.
Imports got less mysterious
Two related fixes, both from the same root cause: the import finished but the screen did not admit it.
The directory now refreshes when an import receipt lands, and the banner waits for a genuinely completed status rather than firing early. If you have ever imported contacts, seen nothing change, and imported again to be safe, that was this bug.
.vcf files also import now, through the same pipeline as CSV. Exports from a phone contacts
app work without conversion.
Chat commands that did the wrong thing
The unglamorous half of the month. In rough order of how much damage each one could do:
| What broke | What it did | Status |
|---|---|---|
| update_lead_value | Accepted $0 as a real deal value and wrote it over the true number | Rejects placeholder writes |
| Participant tools | Rejected valid transaction ids, so deal commands failed for no visible reason | Accepts both id types |
| promote_lead_to_transaction | Same class of id mismatch | Accepts contact and transaction ids |
| Anniversary flags | Congratulated clients on closings that had not happened yet | Guarded for future and sub-one-year dates |
| read_deal_document | Used the wrong prompt and cached the refusal, so retrying failed identically | Correct prompt, no poisoned cache |
| Held receipts | Notices vanished from the overlay before you acted on them | Durable held notices |
Release notes that only list features are marketing. The fix list is the more useful half,
because it tells you what the software was quietly getting wrong while you trusted it. The
$0 bug is the one I would want to know about as a user. It did not throw an error. It wrote
a wrong number into a real deal and looked successful doing it.
Smaller things
- Setup health. A workspace audit that finds decayed config, like a disconnected email account or a campaign pointing at nothing. Ask the assistant for it.
- Campaign exclusivity. Enrolling a contact in a campaign can now stop their other campaigns in the same move, so people stop receiving two conversations at once.
- License number field. Added to your profile. Requested by a tester.
- Contacts sorting. A visible sort control on the directory. Newest, name, last contacted.
- Sidebar scrolling. The nav is its own scroll region, so a long list stops dragging the page with it.
What we did not get to
Ad performance reporting, because Meta did not approve the read permission. That is the honest gap this month, and it stays open until the next review round.
Closr is a CRM you run by talking to it. Nothing to learn, no setup weekend.
Start a free trialQuestions people ask
- Can I keep my existing phone number when I move to Closr?
- Yes. Settings has a porting wizard that collects your number, your carrier account details, and a recent bill. You sign the letter of authorization in the app. Carrier porting takes days to weeks and that part is outside our control.
- Can Closr publish Facebook ads now?
- Yes. Meta approved the ads_management and pages permissions in August, so ad publishing is live rather than draft-only.
- Can I tag a large group of contacts at once?
- Yes. Select all matching a filter and apply a tag to the whole set, or apply tags during a CSV import so contacts arrive already sorted. Explicit lists are capped at 500 per request.
- Does Closr import vCard files?
- Yes. As of August, .vcf files run through the same import pipeline as CSV, so exports from a phone contacts app work directly.
- Where do I see Closr's release notes?
- Here, monthly. Every entry maps to real merged code, including the fixes for our own mistakes.
Closr is a CRM you run by talking to it. Nothing to learn, no setup weekend.
Start a free trialRead next
- Follow Up Boss alternatives: an honest comparison from someone who uses itChoosingI ran a 58,000-contact Follow Up Boss account for years. Here is what it does better than anything else, where it quietly fails, and when switching is a bad idea.
- How to switch CRMs without losing your databaseChoosingYour contacts are the easy part. What breaks in a CRM migration is the history, the tags, and the trust you had in your own data. Here is how to move without wrecking it.
- What to do with 2,000 contacts you have never calledOperatorEvery agent database has a dead zone: hundreds or thousands of people who went in and never came back out. Here is how to work through it without pretending you will call all of them.
One email a month. No drip.
New posts, what shipped, and the occasional thing we got wrong. Unsubscribe in one click.