Swan now watches your prospects' websites
Company websites are where reality shows up first — pricing, packaging, new products, security pages, careers. Swan can now read the recent changes on any company's website and act on the ones that matter, in two ways: an on-demand lookup in chat, and a new scheduled trigger type called Website Changes.
Ask right now, no setup — In chat, ask Swan what recently changed on a set of company domains — for example, "did any of the companies in this list change their pricing recently?" Swan answers immediately from observed change history; it does not need a prior baseline or an existing trigger. Each result includes the changed URL, the change date, a description of what changed, and what it implies — so it works as a prospecting motion, not just monitoring.
The Website Changes trigger — Create one from Triggers → New trigger → Website Changes. Choose the companies to monitor by combining explicit domains (including CSV import), HubSpot company lists (membership is re-resolved on every check), and filters over companies already in Swan — revenue, employee count, owner, funnel stage, target market, and tags. New companies that enter a monitored tag or list are picked up automatically. Checks run daily, weekly, or monthly at a time you choose.
A plain-language change filter — The trigger takes a natural-language description of which changes should wake Swan up, for example: "Pricing, packaging, plan limits, or free-trial changes. Ignore cosmetic redesigns, copy-only edits, and customer-logo updates." Every detected change is evaluated against this filter before your instructions run, so irrelevant changes are filtered out without spending agent time. Swan works from interpreted change events — what changed, where, and its implication — not raw HTML diffs. Evaluating a newly reported change costs 1 credit whether it matches or is filtered out; quiet, unchanged, and excluded checks are free, and an already-evaluated change date is not re-charged.
When a change matches — Swan starts your configured playbook with the domain, changed URL, date, description, implication, and the reason it matched. From there your instructions take over: research the change, find the decision maker, check CRM history, draft outreach for review, notify Slack, update the CRM — whatever you've defined. Each check is recorded in the trigger's run history with an explicit outcome (matched, filtered out, unchanged, missing data, or company excluded), so you can tell a quiet website from missing coverage or an overly narrow filter.
Improvements
Bulk phone enrichment — Phone number lookups now run through a waterfall of multiple data providers and process contacts in batches instead of one at a time. Coverage is noticeably better, and list-scale enrichment is much faster.
Enrich from an email address — Contact enrichment can now build a full profile starting from just an email address, in addition to a LinkedIn URL or a name plus company.
Larger business-event watchlists — Business-event triggers can now monitor up to 2,000 companies per trigger, up from the previous cap.
Sender reconnection recovery — Sequence contacts who were already contacted before a sender disconnected now resume through the normal sending-limit queue after the sender reconnects.
Fixes
Paragraph spacing in sequence emails — Outbound sequence emails no longer collapse paragraph spacing when rendered.
Empty message bodies — An empty email or LinkedIn message body is now rejected at the approval step instead of failing later at send time.
Enrichment with no provider match — Contact enrichment no longer fails the whole request when a data provider returns no person record; it continues with the remaining providers.