Built in public. Improved with purpose.

You can paste screenshots into chat and attach CSV exports from your MLS.

What changed

Pasting a screenshot into chat now works like attaching a file, and CSV files from MLS systems are accepted.

What it means for you

You can show Halo what is on your screen or hand over a listing export without the upload failing.

The main chat could not paste screenshots, and it rejected CSV exports from MLS systems. Clipboard images now attach through the same path as other files, and CSV files are accepted so Halo can read the listing data in them. Chat tiles show the file name, and the upload limit is stated plainly.

Customers reported both problems through in-app support tickets: pasted screenshots not attaching, and CSV exports from their MLS being rejected.

Your new site ships with privacy and terms pages that keep their wording.

What changed

Every new site now includes a privacy policy, a terms of use page and an Equal Housing Opportunity footer, and Halo restores the exact legal wording at every publish.

What it means for you

Your site comes with the compliance basics on day one, and no edit can quietly change the legal text.

New listing sites, agent portfolios and custom sites all start from the same builder, so all of them now include the same legal pages: a privacy policy, a terms of use page, and an Equal Housing Opportunity statement in the footer of every page. Halo fills in your name, brokerage and contact details, and restores the standard wording at every publish so a site edit cannot rewrite it.

A customer whose compliance text already began with the same fair housing statement saw it repeated twice in the site footer.

Your website leads can now go straight to Lofty.

What changed

Lofty is now a destination for your website leads, right from the Leads page.

What it means for you

Choose Lofty and every new website lead lands in the CRM your team already works in.

The Leads page now offers Lofty alongside the other connections. Once it is connected, each new website lead is delivered there with the same receipts, retries and spam filtering as every other destination, and Halo confirms the moment a lead is accepted.

Customers asked for a Lofty connection more often than for any other one we did not yet support.

A CRM connection only saves once it actually works.

What changed

Halo now tests a CRM key or lead address before saving it, explains rejections in plain words, and lets you swap in a new key or address without losing the working one.

What it means for you

You will not see a connection that looks connected but is not, and when something is wrong Halo says what to fix.

Connecting a CRM used to save first and test after, so a bad key could look connected and quietly stay that way. Now the check runs before anything is saved, rejected keys and addresses get a plain explanation, and the Leads page says where leads are going. When a delivery still fails, Halo points you to the fix.

If a site gets too big to build, Halo says so and stays open for edits.

What changed

A site that outgrows the builder now gets a clear, plain-language message and can still be edited, instead of failing with an unexplained error and locking behind support.

What it means for you

You always know what happened, and you can fix it by asking Halo to remove content rather than waiting on support.

When a site no longer fits the builder, Halo now stops and tells you directly that the site is too big and to remove some pages or articles. The site no longer locks, so your next edit to trim it builds normally, and scheduled updates pause only until the site fits again. Nobody has to contact support to get their site moving.

A customer's site was locked behind an unexplained builder failure for 35 hours and required support to unlock.

Partner logos now stay clear and transparent in email.

What changed

Partner logos in co-branded email now keep their transparency and show at a readable size instead of a dark, pixelated block.

What it means for you

When your members open a delivery from Halo, your logo looks the way you designed it.

A transparent partner logo was arriving in some mail apps as a black rectangle with compression damage, and the small display size made fine print unreadable. Logos are now saved so they keep their transparency in email, and the co-brand header shows the logo as large as Halo's own name. The two partners already using co-branding get the fix on their next logo refresh.

A partner's logo came through a mail client with a black background and blocky damage in a report preview.

Your visitor numbers stay current while the tab is open.

What changed

Website analytics on your dashboard now refresh themselves instead of showing a stale seven-day range in a tab you left open.

What it means for you

You can trust the numbers you see, even if you have been looking at the page for a while.

The visitor chart used to load only when a site page opened, so a tab left open kept showing old numbers even though new data was available. The chart now refreshes on its own while you are looking at it and updates the moment you return to the tab. Your dashboard always shows where your traffic stands.

Raised through a support ticket asking why the visitor chart on an open site view had not updated.

New site checks stop blank boxes and washed-out logos before they ship.

What changed

Halo now checks every new site and edit for two broken-look failures, a blank embedded search box and a recolor fill on a logo with no transparency, and refuses to publish them.

What it means for you

Your site never publishes with an empty box where search should be or a logo that renders as a solid rectangle.

Two ways a site could come out looking broken, a home search embedded where the provider does not allow it and a color fill on a logo without a transparent background, are now caught before anything goes live. Halo rebuilds instead of shipping the broken version. The fix applies to new sites and to every edit, so what you publish keeps getting cleaner.

Found in review of live partner sites, where a home-search page was framed into a blank box and footer logos were rendering as solid white rectangles.

Keep your site out of search until you say it is ready.

What changed

You can now ask Halo to keep a site out of search engine results while you finish it, and ask to put it back in search when it is done.

What it means for you

You can polish a site for as long as you need without half-finished pages appearing in search.

Some sites need to be public before they are ready to be found. Halo now saves your search choice with the site itself, so it survives every edit, new page and rebuild, and it reverses whenever you ask. One honest note: the page stays online for anyone with the link, so this is a search setting, not a way to hide the address.

A checkout code now belongs to the same partner as its keyword.

What changed

A word can no longer be shared by two partners as a checkout code on one side and a text keyword on the other, so the code customers are given at checkout is no longer refused.

What it means for you

When someone sends you a checkout code, it works, and no two partners can accidentally block each other's customers.

Halo recognizes partners two ways: a text keyword and a checkout code, and a word should mean the same partner in both. A coupon used to be checked only against other coupons, never against keywords, so one word ended up owned by two partners and a partner's customers were refused at checkout. Now a word belongs to one partner across both, and the one live clash was resolved the same day.

A partner's customers were refused the checkout code they had been given, which exposed the gap between codes and keywords.

Your dashboard picture now updates after every edit, every time.

What changed

Each publish now schedules a fresh dashboard picture that keeps trying until it succeeds, so no live site is left without one.

What it means for you

Your dashboard always shows what your site looks like right now, and you can see your changes landed without opening the site.

A site's dashboard picture was taken in a single attempt after each publish, and when that attempt failed there was no second chance. That left 35 live sites with no picture at all, and edited sites could quietly keep an old one. Every publish now schedules the picture properly and retries until it is done, so the dashboard shows your site as it is.

You can now open a support ticket by text or chat.

What changed

Support tickets are now open to every customer, and resolved answers come back in the same conversation where you asked.

What it means for you

When something needs a person, you can ask for one and follow the issue to a resolution without losing the thread of your chat.

Halo is the place you text, and sometimes the right answer is a tracked issue with the team behind it. Ticket intake was limited to a pilot; now every customer can open one, see its status and close it from the same text or web chat they already use. When the team resolves it, the answer arrives in that conversation.

A customer's request for help never became a ticket, and closing that gap is what opened intake to everyone.

Your site's visitor numbers load right away.

What changed

The analytics view on your site detail page now loads quickly even during busy hours, instead of sometimes showing an unavailable message.

What it means for you

You can check how your site is doing without waiting or hitting an error.

The visitor numbers on your site detail page could slow down and occasionally fail to load when the system was busy. That view now comes back almost instantly, with the same counts as before.

Checkout starts with the card you already have on file.

What changed

One-off purchases, like ordering a listing site or restoring images, now open on your saved card instead of a blank card form.

What it means for you

You can pay in fewer steps, and someone helping you can complete a purchase without ever seeing your card number.

When you buy something extra from Halo, the payment screen now shows the card you already use for your account. The buyer still taps Pay; nothing charges a card on its own.

Partner earnings now count on paid site orders.

What changed

Eligible paid listing and agent-site orders now record the commission they earn for the partner who referred them.

What it means for you

If you referred a customer who paid for a site, you now receive the earnings you were owed.

Some paid site orders were completing without recording the affiliate commission, so eligible purchases earned partners nothing. Commissions now accrue the moment payment is recorded, with the same safeguards against duplicate charges.

Delete a contact, and see which leads you've already reached.

What changed

The Leads page now lets you delete a contact for good, and contacted leads show a distinct badge.

What it means for you

You can keep your leads list clean and tell at a glance which contacts you have already followed up with.

Contacted leads now carry a clear badge so they stand apart from closed ones, and each contact's page has a Delete button. Deleting removes the inquiry, notes, reply draft and activity for that contact; anything already delivered to your email or CRM stays.

Your recurring Smart Update can now keep the day you asked for.

What changed

Recurring Smart Updates can now be pinned to a specific weekday or date, so the schedule you set stays instead of drifting.

What it means for you

If you want your update to run on a particular weekday or date, it now stays there.

Weekly and monthly Smart Updates used to pick their own days, so a schedule you moved to Friday or the 1st would drift back on the next run. Halo now lets a recurring update keep the day you chose, on the weekly and monthly schedules that support it.

Partners can now get credit for sales even when the code was forgotten.

What changed

Halo can now assign, replace, or clear the affiliate on an existing customer's account, even after payment, and credit eligible past payments to the right partner.

What it means for you

If a customer forgets their code before subscribing, the partner can still be credited for that sale.

Until now an affiliate link was locked once a customer paid, so a forgotten code meant a lost commission. Staff can now correct the link after payment and credit eligible historical payments, with earnings preserved for whoever actually earned them.

Your edits are no longer lost when the builder is briefly unreachable.

What changed

When the service that builds sites was briefly unreachable, Halo used to give up and cancel the edit. It now waits and retries until the service recovers.

What it means for you

If you text an edit during a short outage, it goes through instead of being cancelled.

On one day a single very large site stalled the service that builds sites, and 47 customer edits were cancelled before it recovered. Halo now waits out short outages instead of cancelling, so a texted edit survives.

Listing videos now work for land and outdoor-only properties.

What changed

Listing videos can now be planned from land, aerial, exterior, and interior photos, instead of requiring a house facade and three interior rooms.

What it means for you

If your property is land or mostly outdoor views, you can now order a listing video for it.

The video planner used to require a facade and three interior spaces, which blocked listings that were land or outdoor-only. Halo now plans tours from whatever usable views the property actually has, so land and outdoor properties get videos too.

Your affiliate page now works on every device, and you keep the credit.

What changed

The Start free and Start Pro buttons on your affiliate page now work on every device and always carry your code, and the page no longer sends visitors over to Halo's main site.

What it means for you

Everyone who visits your page can start, you get credited for the visits you earned, and no one is redirected away from you.

A partner's page confirmed the problem was everywhere: Start free did nothing on a computer, and Start Pro sent visitors to a page they could not use, dropping both the visitor and the partner's code. Now every button works on every device, the code rides along in the text, and the page keeps visitors instead of linking them away to Halo's main site.

A partner reported that the Start free button did nothing from her computer, which led Halo to test every button on every affiliate page.

Your Halo Hub is one link that tells people and AI assistants about you.

What changed

Halo Hub is here: a public page that gathers your name, sites, listing films and contact into one link, with an Ask your AI about me section.

What it means for you

Put one link in your bio and anyone, person or AI assistant, can learn who you are, see your work and reach you.

Halo Hub is a link-in-bio page for paying members, published at hubs.withhuzi.com/your-link. Halo drafts it from what it already knows: your name, your sites, your listing films and how to reach you. You pick your link, approve the page and publish it from the dashboard, and an Ask your AI about me section lets people and AI assistants get a clear answer instead of a guess.

Your edits are no longer lost when they happen close together.

What changed

Edits that happened close together used to overwrite one another, and interrupted work could fail on retry; Halo now applies changes in order and resumes where it left off.

What it means for you

Everything you ask Halo to change gets saved, no matter how many requests arrive at once.

When several changes were requested around the same time, a finished edit could quietly lose its place to a newer one, and a site that hiccuped mid-work could fail again on retry. Halo now applies edits one at a time in order and resumes interrupted work instead of repeating the failure. Nothing you asked for is dropped by timing.

Order a listing site on its own, without video.

What changed

Listing website orders no longer require a video walkthrough. There is now a website-only choice, and a single exterior, aerial, or land photo is enough to start.

What it means for you

If you want the site now and the video later, you can order just the site.

Listing orders used to require a walkthrough plan and video before anything moved. Now there is an explicit website-only choice, and one good photo is enough to get the order started. Video work is skipped entirely for these orders, so nothing extra is generated.

Partner commissions get paid once your payout account is ready.

What changed

Commissions a partner earned before connecting a payout account are now paid automatically the moment that account is ready.

What it means for you

If you refer business to Halo as a partner, money you earn gets paid to you as soon as your payout account is set up, with no hand-run steps in between.

One partner was owed more than three thousand dollars in referral commissions, and the money sat unpaid for seven weeks because the payout account was attached only later and nothing ever went back to settle the earned amounts. We found it, paid it in full, and built a process that pays waiting commissions automatically once a payout account is ready. Refunded charges close out cleanly, and anything unusual is held and reported instead of skipped.

A partner's payout account was attached weeks after the commissions were earned, and the money stayed marked as owed with nothing revisiting it.

Editing works again for big sites with many pages.

What changed

A safeguard that stopped edits on very large websites was raised, so sites with more than a thousand hand-written pages can be edited again.

What it means for you

If your site has a lot of pages, you can keep editing it by text without it locking up.

A customer's site grew past a thousand real, hand-written pages, and Halo stopped being able to edit it. Every change failed, and after three tries the project locked up for two days. We checked every live site, raised the guard that was in the way, and their edits work again. No other live site was close to the boundary that caused it.

A customer whose site had grown past a thousand hand-written pages reported that every edit failed with an upload error. It was the second customer to hit the boundary.

Your AEO fix-plan request now gets a text back.

What changed

When you ask for a fix plan after an AEO check, Halo texts you directly with your score and the next step, instead of the request going into an inbox.

What it means for you

You hear back in the text thread where you already talk to Halo.

The free AEO check on the Halo site offered a text-me-the-fix-plan form, and those requests landed in an email inbox nobody answered: 21 requests since early September, 18 of them from existing Halo accounts. Now the request reaches Halo directly and you get a text back matched to your situation. A perfect score gets congratulations and no pitch. A Halo-built site under 100 gets an offer to start on the fixes. Any other site gets the report and an authority page offer.

People who ran a free AEO check and asked for the fix plan by text received nothing; 18 of the 21 unanswered requests came from existing Halo accounts.

The Captain's log updates every Sunday night.

What changed

The public log at huzihalo.com/log now publishes on a steady weekly rhythm instead of sitting frozen for weeks.

What it means for you

You can count on a fresh, honest update from us every Sunday, and it reads as plain outcomes, not a tour of our machinery.

The log had stopped updating, with the newest entry weeks old. Entries now live in a system that drafts, reviews and publishes every week on its own, and each one is written from the customer's side of the screen first. The public page shares what changed and what it means for you, and keeps the internal how-it-works detail out of view.

Search engines and AI assistants now know what Halo is.

What changed

The public site now shows search engines and AI assistants the same full pages a person sees, instead of a nearly empty page.

What it means for you

When someone searches for a marketing agency, or asks an AI for one, they can now find the real Halo and real details about what we do.

Search engines and AI assistants used to see almost nothing when they visited huzihalo.com, so Halo could not be found or described accurately. Now every public page is written out in full for them, with a clear description, and the whole site is mapped and listed. People and search tools get the same site, and an independent readiness check climbed to a perfect score.

A missing icon was being reported as a memory failure, and it locked projects.

What changed

A build that failed on a one-word source error is once again handed back to the agent to fix, instead of being declared unfixable.

What it means for you

A tiny mistake in a page no longer ends in a locked project and an email to support.

A new site failed three times in forty minutes and locked, and the customer was told to email support. The real defect was one word: an icon name that does not exist. A safety check had misread an ordinary word in a page address as a sign the build had run out of memory, and Halo trusted that verdict. Over thirty days, 21 missing-icon failures across about nine customers were labelled unfixable the same way. A real error message now always wins over a guessed label, and the check itself was corrected the same day and rolls out with the builder’s next deploy.

Partners can sync their referrals into their own CRM.

What changed

The partner dashboard can send referral and subscription events to a CRM webhook, with GoHighLevel setup documented step by step.

What it means for you

If you refer agents to Halo, their status lands in your CRM automatically instead of in a spreadsheet.

Enterprise partners now connect a CRM webhook from their Halo dashboard. New referrals, subscription changes and cancellations are delivered as events with the contact’s phone, email and name, plus the fields a workflow needs. A sample send and a sync of existing referrals make setup testable, and automatic syncing is on by default for new connections.

Every account has a creative allowance, and now we say so.

What changed

Social posts, flyers and market graphics come from a monthly creative allowance on Halo Pro and a one-time starter allowance on Halo Start, and the site and the assistant now explain it.

What it means for you

You know what is included before you ask for a graphic, and a free account can make its first social posts and a flyer.

Halo Pro includes a monthly creative allowance for graphics in your brand, refreshed on the first of the month, with a top-up by text if you run out. Halo Start accounts, which previously could not generate images at all, now have a one-time starter allowance for social posts and a flyer. The pricing page, the comparison table and the FAQ describe both.

The new huzihalo.com is live.

What changed

The public site now shows real work, real numbers and this log, and runs a free AI-visibility check on any website from the homepage.

What it means for you

You can see what Halo has built for others, check how visible your own site is to AI, and get the full report by text.

Halo’s public site moved from a prototype to production: the homepage, case studies, pricing, site styles, the Field Report and this log. The homepage runs a real AI-visibility audit on any website you enter, shows the score, and texts you the full report if you ask. A reply of BUILD starts a free site from the report. The numbers on the site are counted from Halo’s own records every day.

One edit took Halo down for two hours. It cannot happen again.

What changed

Heavy work for one customer’s edit now runs in its own protected space with limits, so it cannot stall Halo itself, and an automatic restart only stops the stuck work.

What it means for you

A runaway command in one customer’s edit can no longer stop your texts, your login or your dashboard.

On September 9 an ordinary edit, a request to repair corrupted characters across a site, led the agent down an extremely slow path that consumed Halo itself. Nothing answered for about two hours (5:58 to 7:53 AM Pacific), and each automatic restart picked the same edit back up. Work like that now runs in its own protected space with memory and time limits, and a step that gets stuck becomes an error the agent can work around instead of an outage.

Content that fades in can no longer stay invisible.

What changed

Fade-in animations now start visible and only hide content once the page is ready, and the builder blocks any page whose animated content stays hidden.

What it means for you

A long article or blog list on your site cannot disappear behind an animation that never fires.

Fade-in effects hide a section until it scrolls into view. On a tall blog list or a long article on a phone, that moment could never arrive, so whole sections stayed invisible. Content is now visible by default, long sections are never hidden behind an animation, and every deploy is checked in a real browser for content that stays hidden.

Your exact words stay your exact words.

What changed

When you ask for copy to be placed word for word, Halo transfers your original message instead of retyping it, and cancelling an edit now targets the page you name.

What it means for you

Compliance-approved or locked copy lands on your site exactly as you sent it, and stopping one page’s edit no longer stops the others.

If you say verbatim, word-for-word or locked copy, the edit now carries your original message through untouched; the model only writes the placement instructions. Saying stop or cancel cancels the edit instead of accidentally creating another one, and naming a page limits the cancellation to that page. A failed site build can now be retried and resumes where it left off, and a mistyped project reference is corrected when exactly one of your projects matches.

Stray control text from the model no longer reaches your messages.

What changed

Stray control markup from the model is caught before it can be shown, saved or acted on, and 31 older conversations were cleaned.

What it means for you

You will not see odd tags in a reply, and no edit can be triggered by garbled instructions.

The model behind chat occasionally slipped pieces of its own control markup into a reply. Halo now catches that before anything is shown, saved or acted on, and retries the step cleanly. On September 7 the same cleanup was applied to 31 older conversations that still carried that markup, without losing any of their real history.

Send Halo a PDF and it reads it.

What changed

PDF attachments in chat are now readable, including scanned documents, and a brand-guidelines PDF is carried into a website order.

What it means for you

You can text a brochure, a brand guide or a scanned document and ask about it, or have a site built in that style.

Attach a PDF in chat or iMessage and Halo extracts the text (or reads the page images when there is no text layer) and answers your question from it. Only the answer enters the conversation; the document itself stays private to the reader. When the PDF is a brand guide, the colors, fonts, logo rules and tone flow into the normal website order.

Event keywords now come with a set of included changes and a coach.

What changed

Each live-event keyword is its own campaign: one free site, a set number of included changes, and a suggested next edit after every deploy.

What it means for you

If you text a keyword from an event, you get a real site, a clear number of included changes, and a suggestion for what to improve next.

The August experiment became a system. Every keyword is configured on its own terms, and the newer campaigns include a coaching layer: after the site is built and after each change goes live, Halo suggests one edit aligned with the goal you told it. When the included changes are used up, it explains what daily marketing with Halo looks like and sends a checkout link. Anyone who texted earlier keeps the terms they were given.

An edit no longer dies on a typo.

What changed

Every page is checked for errors before a build is even queued, and a fixable build failure now gets more chances to be repaired.

What it means for you

More of your edits finish the first time, and a small syntax slip is fixed for you instead of ending the run.

Halo now checks every page for errors before a build is queued, so a small slip is caught and fixed at once instead of failing later. A repair that has not fully landed no longer ends the run early, and a run that stops short of finishing is nudged to complete.

Halo no longer guesses an image address.

What changed

Image addresses are never guessed, and pictures from your existing site or a link you send are brought over intact.

What it means for you

Fewer broken pictures on your site, and photos from your own existing site can be brought over intact.

Over two weeks, 258 broken images on customer sites traced back to one habit: the agent typing an image address from memory instead of using the real one. Halo now uses only addresses it has actually seen, and when a picture lives on your existing site or at a link you send, it brings the file over intact. YouTube thumbnails are recognized as valid images.

Your requested edits now move to the front.

What changed

Customer-requested edits now receive priority over background builds and scheduled work.

What it means for you

When you ask Halo to make a change, you should see it sooner.

We reorganized how Halo prioritizes its work around who is actively waiting. Requested edits now move first, followed by new sites and scheduled background work.

Publishing is ready for the next thousand sites.

What changed

Every customer site is now served through one shared server configuration, so publishing a site no longer reloads anything.

What it means for you

Your site goes live faster, and it stays fast no matter how many other sites publish in the same hour.

Each site used to carry its own server configuration, and every new site forced a reload that held up the builds behind it. Now one configuration serves every site and a publish is an instant swap, so busy hours no longer slow anyone down. It took one reload to retire 1,474 old configurations, and the ceiling we were heading toward is gone.

The right model for each job, and no surprise changes overnight.

What changed

Chat, site building, video, background tasks and image checks each run on their own model, and every model is pinned to a dated version.

What it means for you

What Halo writes and builds for you stays consistent from one day to the next, and improvements can be rolled out one job at a time.

Chat, site building, video, background tasks and image checks each run on their own model slot, switchable from the admin panel. We retired the model we launched on and pinned every replacement to a dated version, so a provider’s silent update cannot change what customers get overnight.

A deploy in the middle of the day costs you nothing.

What changed

An edit saves its place after every step and resumes from there after a restart, and every safety timer is now sized from real, healthy runs.

What it means for you

Your edits survive our deploys and restarts, and healthy work is no longer cut short by a timer set on a guess.

An edit now saves its place after every step and resumes from there after a restart; a build that was already accepted is re-attached, not re-run. Every safety timer was re-sized from measured healthy runs, Smart Updates moved into an overnight window spread across weekdays, and staff got a switch to pause a runaway conversation without losing anything.

We removed a video worker that never did what it claimed.

What changed

A separate video rendering process introduced in June was removed after an audit showed it did not isolate heavy renders as intended.

What it means for you

Nothing changes in what you receive; the code that runs your films is now honest about what it does.

In June we split video rendering into its own worker process, believing it isolated heavy renders from the rest of the service. An August audit showed it didn’t. The code is gone.

A site whose data just got shorter cannot publish.

What changed

The site editor now appends to data files with a proper tool, and the deploy gate refuses any build whose data array is smaller than the live site’s.

What it means for you

An edit can no longer wipe your listings, posts or guide entries by accident.

The site editor tried a shell shortcut to add an entry to a JSON file; the sandbox didn’t support it, and the redirect emptied the file before the error surfaced. It happened twice. The editor now appends with a proper tool, and the deploy gate refuses any build whose data array got smaller than the live site’s.

Two incidents on customers’ guide sites, Aug 20 and Aug 23.

Your listing site is not on a timer, and your edits are not counted.

What changed

We removed a line promising “1 year of hosting and 5 revisions” from the assistant and from a draft of our terms, because neither limit ever existed.

What it means for you

Your listing site stays published and you can keep editing it by text, with no clock and no cap to keep track of.

A leftover product description had been copied into the assistant’s instructions and from there into a draft of our terms. No site has ever been taken down on a timer and revisions were never counted: the average listing site has been edited by text 10.6 times, and 217 of them have passed five. We removed the numbers and committed to none.

Text a keyword at a live event and get a free site.

What changed

Texting one keyword during a live talk unlocks one free niche site before the paywall, and the unlock is announced by the system rather than noticed by the assistant.

What it means for you

You can try Halo from the audience and have a real site started before the talk ends.

For a live talk, texting one keyword unlocked one free niche site before the paywall. Fifty-seven people texted it in about eighty seconds. The first two versions relied on the assistant noticing the code in conversation, and it didn’t, twice. The version that works announces the unlock deterministically and sends people into the same step-by-step wizard everyone else uses.

Halo picks the wrong action less often.

What changed

The assistant’s three ways to start a project and three ways to restart one became one of each, and its instructions are about a third shorter.

What it means for you

When you ask for a site, Halo is less likely to start the wrong kind of project or take the wrong path.

The assistant had three creation tools and three restart tools. It now has one of each, and its system prompt is about a third shorter. On our 89-check evaluation it scored the same; in the wild it picks wrong less often.

No single video request can take the whole service down.

What changed

Every video tool call is now time-bounded and re-renders default to the tier the customer paid for.

What it means for you

One unusually heavy request can no longer stall everyone else’s films and texts.

The video agent did exactly what it was asked and rendered thirty clips at 4K until the service ran out of memory, 194 times in two hours, because the retry loop had no give-up. The day before, a hung encoder had wedged the video queue. Every video tool call is now time-bounded and re-renders default to the tier the customer paid for. A hard resolution ceiling is next on the list.

Halo looks things up before it writes.

What changed

Web search is on for every subscriber, so Halo checks current facts before writing content.

What it means for you

Ask for this week’s rates, a school ranking or what’s happening downtown Saturday and the answer is current, not a guess.

Ask for this week’s rates, a school ranking or what’s happening downtown Saturday and Halo looks it up before it writes. It shipped as a staff experiment on Aug 3 and went to every subscribed account three days later.

Long work no longer gets cut off mid-conversation.

What changed

Image generation runs as background jobs beside the conversation, and the chat watchdog is sized from real turns.

What it means for you

Asking for several graphics at once finishes, instead of being stopped by a safety timer while it is working.

On Aug 3 our own chat watchdog killed the most productive turn of the day: a customer asked for four social graphics, each took about two and a half minutes, and the ten-minute ceiling fired on a turn that was working. Image generation now runs as background jobs beside the conversation, and the watchdog is sized from real turns.

Every order is one step-by-step wizard.

What changed

Listing sites, smart sites and niche sites all order through one wizard that asks one question at a time and keeps your answers through a refresh.

What it means for you

You pick style and photos before you pay, and you never face a twelve-question form.

Listing sites, smart sites and niche sites all order through the same wizard: one question at a time, answers that survive a refresh, style and photos before payment. The rework also deleted the “Update plan” button, and a customer found that before we did. Restored two days later.

Your custom domain works with and without www.

What changed

Attaching a domain now provisions the apex and the www address together.

What it means for you

Visitors who type www in front of your domain reach your site instead of an error.

A July audit found 81 customer domains whose www record pointed at us with nothing to answer it, because our instructions only mentioned the apex record. We backfilled 77 www certificates that day; on Aug 4 attaching a domain started provisioning apex and www together.

Per-site image budgets: shipped in the morning, pulled the same day.

What changed

Per-site image allowances shipped and were taken down within hours.

What it means for you

You were not asked to understand a limit we could not yet explain in one sentence.

We built and shipped per-site image allowances, then took them down within hours. The accounting was right; the product idea wasn’t ready, and shipping something we’d have to explain to a thousand people is worse than waiting.

A site that scrolls sideways on a phone cannot publish.

What changed

The builder measures every page at phone and desktop width and refuses to publish one that overflows.

What it means for you

Your site stops shipping with a layout mistake that only shows up on a phone.

Three one-line CSS mistakes, invisible on desktop, made pages scroll horizontally on phones. The builder now measures every page at phone and desktop width and refuses to publish one that overflows. A quarter of the sites we sampled already had the problem; each gets fixed on its next edit.

Halo builds for salons and restaurants too.

What changed

The assistant’s instructions no longer describe Halo as a real-estate-only tool.

What it means for you

If your business is not real estate, Halo builds your site instead of turning you away.

The assistant refused to build sites for a salon, a restaurant and a meditation practice because the prompt described Halo as a real-estate tool. The first fix reached one branch of the prompt and missed the other; the second landed two days later.

A published site is never rebuilt from its template by a recovery.

What changed

A recovery path meant for interrupted builds could regenerate a finished site from its template; the rule is now absolute that it cannot.

What it means for you

Your blog posts, pages and custom pieces cannot be discarded by a recovery step.

A customer reported edits disappearing. Nothing was reverting: a recovery path meant for interrupted builds had “resumed” a finished site by regenerating it from its template during a busy deploy afternoon, discarding eleven blog posts, two pages and a custom widget. We restored the site by hand and made the rule absolute: a published site is never rebuilt from its template by a recovery.

An automation that cannot do the thing says so up front.

What changed

The scheduler refuses any Smart Update instruction that depends on human approval, and says why when it is created.

What it means for you

You will not be told an automation will hold drafts for review when it cannot.

A customer asked for weekly posts saved as drafts for review. The automation has no drafts and no email, so it did the only thing it could and published them. The scheduler now refuses any instruction that depends on human approval, and says so when it’s created.

“Nothing to change” is no longer reported as a failure.

What changed

When a site already matches a request, Halo reports that honestly instead of calling the edit failed.

What it means for you

You stop retrying and escalating an edit that had already succeeded.

When a site already matched a request, the system reported the edit as failed. Customers retried, then escalated; one evening produced four support referrals for a site with zero defects. “Already in the requested state” is now its own honest outcome.

One image tool for everything.

What changed

Flyers, market graphics, virtual staging, headshot touch-ups and video stills all go through one image agent that picks the model for the job.

What it means for you

Whatever you ask for, the result is made the same careful way, with one place keeping track.

Flyers, market graphics, virtual staging, headshot touch-ups and video stills used to run through three tools with three sets of rules. Now every surface, chat, site builder and video, calls one image agent that picks the model for the job, with a single spend ledger behind it. Virtual staging by text shipped the same month.

Leads flow into the CRM you already pay for.

What changed

Zapier, GoHighLevel and custom-webhook add-ons send every inquiry to the system you already use, installed by text.

What it means for you

Every lead lands where you already work, with nothing to copy over.

Zapier, GoHighLevel and custom-webhook add-ons send every inquiry to the system an agent already uses, installed by text. By the end of August: 56 Zapier, 67 GoHighLevel and 10 webhook installs.

Replacing a logo broke 123 sites. Now nothing is ever deleted.

What changed

Uploading a new logo or headshot no longer deletes the old file; every brand asset is versioned with history and restore.

What it means for you

Your published sites keep showing the right images no matter how many times you change your brand.

Uploading a new logo used to delete the old file, and with it every published site still pointing at it. We restored the originals, replaced 2,512 dead links across 973 files without a single rebuild, versioned every brand asset with history and restore, and removed every delete from the runtime. Storage only grows now.

The add-ons marketplace is open to everyone.

What changed

Chat concierge, newsletter popup, event banner, lead quiz, animations, hero video, Google Analytics and the Meta pixel install by text or one click.

What it means for you

The things you used to open a support ticket for are now on a shelf you can add yourself.

Chat concierge, newsletter popup, event banner and lead quiz on Jul 8 (staff-only first), Beautiful Animations and hero video on Jul 17, Google Analytics and the Meta pixel on Jul 19–20, each installed by text or one click. One went wrong: an animation add-on blanked seven sites for an afternoon because of how the site framework scopes styles; we hid it, fixed the install and put it back the same day. 953 installs by the end of August.

A page nobody can reach can no longer be created.

What changed

Builds fail when they introduce a page with no link to it, and the assistant checks whether a page is linked before guessing “caching”.

What it means for you

Your edits land on the page your visitors actually reach, and search engines can find every page.

A customer’s edits were landing on the right page while her navigation pointed at a stale near-duplicate. About half the sites we sampled had at least one page nobody could reach. Builds now fail when they introduce an orphan page, and the assistant checks whether a page is linked from the homepage before it guesses “caching.”

An automation that cannot succeed is refused before it is scheduled.

What changed

A capability check runs when a Smart Update is created and allows, warns or denies it with the reason.

What it means for you

You will not set up an automation that quietly fails every week.

We audited every Smart Update and found 37 that could never work: MLS feeds we don’t have, emails nobody could send, duplicates of each other. A capability check now runs when an update is created (allow, warn or deny, with the reason).

A person’s edit always jumps the automated herd.

What changed

Texted edits dispatch before scheduled updates, in their own lane with their own model.

What it means for you

Your change is worked on before the scheduled background updates, even on a busy morning.

The edit queue became priority-aware: texted edits dispatch before scheduled updates. A week later an “aging” rule that let old automated jobs cut back in front was removed; it was starving real people. On Jul 13 edits got their own concurrency lane and their own model.

The morning everything fired at once.

What changed

Recurring updates are staggered per automation, builds are capped and de-duplicated, and the builder queues work instead of timing out.

What it means for you

Your weekly updates still run every week; they no longer all run in the same hour and crowd each other out.

Every recurring update was scheduled naively, so one day the whole fleet ran in the same hour: 152 jobs deep, server out of memory. Fire times are now staggered per automation, builds are capped and de-duplicated, and the builder took an asynchronous submit-and-poll API so a queue is a queue, not a timeout.

Every site is written for AI to read.

What changed

Every deploy ships llms.txt and llms-full.txt, structured data in every page head, and canonical URLs that follow a custom domain.

What it means for you

When a buyer asks ChatGPT who to call, your site is one a machine can read and recommend.

Every deploy now ships llms.txt and a full llms-full.txt, structured data in every page head, and canonical URLs that follow a custom domain. On Jun 15 we also stopped the assistant claiming search work it hadn’t done.

Templates became styles, and “Halo picks” means bespoke.

What changed

Twenty-three templates collapsed into one blank foundation plus a catalog of style guides.

What it means for you

When you let Halo choose, it designs from your brief instead of picking a preset, so your site does not look like everyone else’s.

Twenty-three templates collapsed into one blank foundation plus a catalog of style guides; ten niche styles followed on Jun 24. When a customer lets Halo choose, it designs from the brief instead of picking a preset. Sites stopped looking like each other.

Every lead reaches a real inbox, or your phone.

What changed

Leads go to a verified account email connected with one code, or arrive as a text when there is no email, after a write-up and a spam screen.

What it means for you

Every inquiry gets read, summarized and screened before it reaches you, where you already are.

Text-first sign-up meant some accounts had no email at all, and their leads went nowhere. Leads now go to a verified account email, connected with one code; if there’s no email, the lead arrives as a text. Every inquiry gets an instant write-up and a spam screen first: by the end of August, 1,091 spam submissions quarantined and 1,022 real leads delivered.

Your own domain, by text.

What changed

Text Halo your domain and it replies with the exact records to add, watches for them, and issues the certificate on its own.

What it means for you

Your site lives at an address you own, without a support ticket.

Text the domain; Halo replies with the exact records to add, watches for them every 30 seconds, and certificates issue on their own. 238 customer domains were connected by the end of August.

Smart Updates: work that runs whether or not you text.

What changed

Scheduled work such as weekly market stats, local events, business spotlights, blog rotations and review refreshes runs on its own.

What it means for you

Your site keeps changing, so people have a reason to come back.

Scheduled work that runs whether or not you text: weekly market stats, local events, business spotlights, blog rotations, review refreshes. Members asked for it within days of launch; it shipped on May 25 and came to listing sites on Jun 4. 810 were running by the end of August and had completed 8,135 runs.

Half of our site builds were failing. The agent had gotten too smart.

What changed

A rewrite deleted most of the site agent’s bookkeeping; builds went from 25 to 40 minutes to about five, and a circuit breaker plus auto-resume followed.

What it means for you

Your site builds in minutes and finishes reliably.

By May 22 a personal-site build took 25 to 40 minutes and 244 model steps, compacting its own memory five times, and about half failed outright. Every commit that made it worse was a sincere attempt to make it better. A rewrite deleted most of the bookkeeping; builds went to about five minutes and became reliable, and a circuit breaker plus auto-resume followed on May 27.

Halo opens: subscribe by text, sign in by phone.

What changed

Subscription checkout, phone-code login and an onboarding assistant that starts working before you pay all shipped on launch day.

What it means for you

No app to install and no dashboard to learn: text the number and something starts getting built.

Launch day was a webinar and a phone number. Subscription checkout, phone-code login and an onboarding assistant that starts working before you pay all shipped the same day; the first personal site was built that night. 276 accounts by the end of May.

Picket becomes Halo.

What changed

The listing-site tool got a new name, a real database, on-disk workspaces and a second product line of personal and niche sites.

What it means for you

Halo is now a marketing agency you text, not only a listing-site tool.

The listing-site tool got a new name, a real database, on-disk workspaces and a second product line: personal and niche sites, separated from the listing pipeline. The rebrand had started two days earlier with the new interface.

The whole product moved into iMessage.

What changed

After an in-app chat and a day on WhatsApp, Halo settled in iMessage, the thread agents already live in.

What it means for you

Orders, checkout links, progress and finished work all arrive as texts.

We tried an in-app chat on May 7, moved to WhatsApp the next day, and landed in iMessage on May 14, the thread agents already live in. Orders, checkout links, progress and finished work all arrive as texts.

A site that fails its own inspection does not ship.

What changed

Every deploy is opened in a real browser at phone and desktop width and checked before a customer sees it.

What it means for you

Most of what the inspector catches is what you would have texted us about an hour later.

Strict builds began with internal-link verification and kept growing: rendered-asset checks, first-party console errors and stock favicons in July, orphan pages on Jul 16, content regressions on Jul 21, phone-width overflow on Aug 3. Every deploy is opened in a real browser at phone and desktop width before a customer sees it.

Edits by text, queued.

What changed

Website edits became a queue you can add to as fast as you can type, with a cancel button for anything in flight.

What it means for you

Say the change and Halo makes it, in order, while you keep texting.

Website edits became a queue you can add to as fast as you can type, with a cancel button for anything in flight (Apr 29) and prompt-based video corrections (Apr 26). The document vault shipped the same day. 59,217 edits were completed by the end of August.

The first listing site and the first walkthrough film.

What changed

Picket built its first property site and cut its first walkthrough film from still photos the day after it started.

What it means for you

A listing can be marketed from an address and a folder of photos.

Picket started on Apr 14. The next day it built its first property site and cut its first walkthrough film from still photos; virtual staging and furniture styles followed on Apr 21, and the film started embedding itself into the site. 432 films by the end of August.