Foxglove Group

Confirmed — third time this year the same thing's happened on a creative tender. Procurement's threshold kicks in at $15k and the policy has no carve-out for a 'continuing creative partner'. The pattern detector is now flagging it as a category — see the analysis below. I'll pull the full spend across all three incidents and Nik can take a scoped proposal to procurement leadership. In the meantime I've asked your Finance Director via Nik whether we can override this round on continuity grounds.

Finance Director is willing to override but wants a written policy proposal she can take to the procurement director. Nik and I will have a draft ready for your review on Tuesday.

Pulled an audit on the last 30 days: the rules catch 73% of duplicate pairs cleanly. The remaining 27% are fuzzy matches — slight name spellings (Maria vs Marya), missing accents (Müller vs Muller), and multi-touch arrivals where a web booking form and an Instagram DM land within seconds of each other. The strict rules don't do fuzzy matching by design; that's not the right tool for that 27%. Two options I'd consider, both with estimates on this thread: (a) a fuzzy-match pre-pass that flags candidates before the strict rules evaluate, (b) replace the rules with a hybrid scoring layer. I'd go (a) — less disruption.

Yeah — and the agent has no way to know the article is stale. There's no last-reviewed metadata, no owner field, no 'review-by' flag. Started a quick spot-check on the top 40 most-viewed Knowledge articles: 31 haven't been edited in 6+ months, 11 are over a year old. Pattern detector is flagging this as a category too — see the analysis below.

Inspected the functions proposal deck — the 'Packages' slide is populated from the Salesforce Knowledge 'Function packages matrix' article. That article was last edited in October '25 and still lists three packages we've since retired. Two options: (1) refresh the source article so every downstream surface picks it up, (2) decouple the deck and maintain it by hand. (1) is what I'd recommend but it needs an owner. Who do you want me to assign?

Spent an hour walking the integration layer with Priya. The audience sync isn't alone — there's a webhook-driven enrichment, a BI export, and the Collins→Salesforce booking sync, all authenticating as individual users (mix of OAuth, named-credential, and one personal key). None on service accounts. The failure mode is silent: works fine until someone leaves, takes leave, or hits a re-auth. I'd want to scope this carefully — each integration has slightly different auth — but the shape of the fix is clear. Pattern detector is flagging it as a category; see the analysis below.

Two compounding issues. (1) Personal Gmail isn't built for this volume of templated sending — reputation tanks once a sender crosses ~150/day for any sustained stretch. (2) The display-name / address mismatch is an SPF/DKIM red flag for the big receivers; that's why the phishing prompt fired. Both close together: move the functions sending onto a dedicated subdomain off foxglovegroup.com.au, warmed, with verified sender profiles in Marketing Cloud. It's the sending infrastructure, not the tool. Sits naturally under the same project as the Priya thread.

There is, and it ties straight to the Knowledge work Jenny's doing. Cross-referenced 30 days of after-hours enquiries: ~68% are repeat questions already answered in Knowledge, and they peak 7-11pm when nobody's monitoring. The move is a guest-concierge agent on Agentforce, grounded on the (refreshed) Knowledge base, live on web chat and Instagram DM, that answers the FAQ tier instantly and hands a qualified function or group enquiry straight to the team with the guest's details attached. Caveat I want on the record: it's only as trustworthy as the Knowledge behind it — so this rides on the staleness fix, not ahead of it. Pattern detector's flagging it; see the analysis below.

There is, and it's the same root cause as the procurement-tender mess and the Knowledge staleness — there's no single governed source of truth for an offer, so every launch is hand-copied across surfaces and one always drifts. Theo and I have a shape for it: run the whole graphic-design tender and offer process as an SOP on a Monday board — brief, bids, award, asset approval — and on approval, automations plus the integration layer push the finished offer to Webflow CMS, Marketing Cloud, and the Salesforce Knowledge article in one move. Approve once, every surface updates. Pattern detector picked it up as its own category — see the analysis below. This is the one I'd most like to walk you through.