Only differences that need a decision reach this queue. Duplicates, more precise restatements and figures that simply grew are merged automatically and recorded in the audit trail — flagging those too would train everyone to ignore this page.
Highcontradiction
Slack notifications recorded as active, incoming says they have stopped
In the knowledge base
Slack notifications are active for both form submissions and appointment bookings
Incoming
Slack notifications from the legacy system have stopped working, leaving the sales team with only calendar entries and no lead details
This is a backwards move in an operational capability, not forward drift. If the sales team has no lead details, leads booked during the lockout are being handled blind and may be lost outright.
Two statements that cannot both be true now.
Options
Highcontradiction
Opt-in form architecture: per-funnel forms recorded as already built, incoming says a single shared form is still in use
In the knowledge base
A unique opt-in form was created for each of the five active funnels so that leads can be tracked at lead level, replacing a single shared form used previously
Incoming
A single opt-in form has been used across multiple funnels, which the agency identified as a source of tracking issues
Lead-level attribution across all five funnels depends on which of these is true. If the shared form is still live, every source-channel figure in the CRM is unreliable and the funnel comparison analysis is being run on bad attribution.
Two statements that cannot both be true now.
Options
Highcontradiction
Webinar length recorded as 60 minutes in the knowledge base, 90 minutes in the incoming batch
In the knowledge base
Runs an existing webinar as part of the funnel, in either a 20-minute or 60-minute format
Incoming
The webinar funnel was switched sequentially from a 90-minute webinar to a 20-minute webinar in December 2025; the decision was made to run the 90-minute webinar funnel for now
The long-form webinar is the funnel the team has just decided to run, and its length is stated two different ways. Nine months of historical performance analysis is being split on this format boundary, so the wrong figure misattributes results — and a webinar advertised at one length and delivered at another is a promise the brand cannot keep.
Two statements that cannot both be true now.
Options
Highcontradiction
Webinar length: existing record says 20 or 60 minutes, incoming says 90 minutes pre-December 2025
In the knowledge base
Runs an existing webinar as part of the funnel, in either a 20-minute or 60-minute format
Incoming
Runs a 90-minute webinar funnel, which was the format in use before December 2025 — and a 20-minute funnel exists on Salesable but is not updated, so the 90-minute funnel will be run instead for now
The webinar length is the spine of the funnel comparison and of the nine-month performance analysis. If the historical period was 90 minutes rather than 60, every before/after conclusion and any client-facing description of the funnel is built on the wrong figure. No passage of time reconciles 60 and 90 for the same pre-December format.
Two statements that cannot both be true now.
Options
Highscope change
Access problem widened from Funnel Web only to both platforms
In the knowledge base
The legacy funnel web account is locked out for both the founder and the agency, blocking lead handling and domain migration — and Salesable treated throughout as the working destination platform held on a paid subscription
Incoming
Neither the founder nor the agency holds owner-level access to Funnel Web or Salesable; both were set up under accounts owned by others
The entire migration plan rests on Salesable being a platform the client controls. If owner-level access to Salesable is also missing, the consolidation decision, the domain move and the course hosting all inherit the same single-point-of-failure that caused this project, and the client could be locked out of the destination too.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Highscope change
Recommendation against granular conversion events conflicts with the pixel setup already implemented
In the knowledge base
Meta pixel is now configured on both the opt-in form and the calendar booking stage; opt-in submission fires a 'lead' event and appointment booking fires a 'schedule' event back to Meta
Incoming
Agency position is that for high-ticket offers Meta performs better with a single consolidated conversion basket than with granular multi-step call-stage events, citing a real estate client whose ad results worsened after over-segmenting
The two-event setup was built to fix the acknowledged pixel problems that were the likely cause of past tracking issues. If the agency's own position is that multi-step events degrade performance for high-ticket offers, the freshly built configuration may be working against the ad account — and leaving both records in place means whoever reads next cannot tell which one governs.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Highcontradiction
Contact volumes conflict across three records and internally within the incoming batch
In the knowledge base
505 contacts were migrated from the legacy funnel web system to Salesable; separately, existing customer/contact database of 9,000 email addresses
Incoming
Over 9,000 contacts exist on each of the two platforms, exported for migration — and, in the same batch, approximately 200 of the contacts originate from Funnel Web with around 8,800 from the older Salesable data
These cannot all be true. 'Over 9,000 on each platform' is contradicted by the same batch's own split of 200 plus 8,800. The Funnel Web-origin count has also moved backwards from 505 to ~200, which no passage of time explains. Migration scoping, the safe-vs-VLOOKUP option choice and any reported database-size figure all depend on getting this right, and an inflated contact count is the kind of number that ends up in a public claim.
Two statements that cannot both be true now.
Options
Highcontradiction
Current funnel described as driving to a live webinar, while the knowledge base records a rebuilt three-step funnel with a pre-recorded 75-minute video and live webinars only planned to resume
In the knowledge base
Step two of the funnel is a 75-minute video followed by calendar booking; Monthly live webinar series, targeted to launch late September or early October; Live webinars are planned to resume with automated reminder emails and WhatsApp reminders set up beforehand
Incoming
The marketing funnel drives traffic to a live webinar, after which prospects can book an appointment directly or be followed up with by the sales team
The funnel step is the single most load-bearing fact for ad copy, landing page promises and the webinar relaunch timeline. If creative promises a live webinar while the funnel serves a recorded video, prospects are misled and the 90%+ show-up figure is being attributed to the wrong asset. The two statements cannot both describe the funnel as it stands today.
Two statements that cannot both be true now.
Options
Highcontradiction
A9 described as consistently generating clients and kept active, but also as turned off early in the newer campaign
In the knowledge base
An ad set labelled "A9" is kept active on the basis that it consistently generates clients
Incoming
A9 was turned off early in the newer campaign and the historical winners were not given long run times
A9 is on the relaunch list as a proven winner. If it was actually turned off early and never given a fair run, the 'consistently generates clients' justification may be unsupported, and the campaign would be rebuilt around a creative whose performance was never established.
Two statements that cannot both be true now.
Options
Highcontradiction
Show-up rate stated as 50–60% against two existing records asserting over 90%
In the knowledge base
Show-up rate for booked appointments is over 90% (also recorded as 'Show-up rate on booked appointments is over 90%')
Incoming
Historical show-up rate on booked calls is 50% to 60%
A show-up rate is a headline performance number likely to appear in proposals, case studies and paid ads. The gap between 55% and 90%+ is not a rounding difference, and shipping both leaves the brand with two irreconcilable public claims. It also feeds cost-per-booking and close-rate maths downstream.
Two statements that cannot both be true now.
Options
Highcontradiction
Single-ad-set CBO structure conflicts with a dedicated case-study ad set split test already on record
In the knowledge base
A dedicated ad set focused exclusively on existing client case studies is being launched, split-tested against newly produced creatives
Incoming
Agency's preferred Meta account structure is one campaign, one ad set, CBO, managing all creatives at the creative level rather than across many ad sets
These are mutually exclusive build instructions for the same ad account. If both stay in the knowledge base, the account gets built one way and reported on the other, and the split test result — if anyone runs it — will not be interpretable.
Two statements that cannot both be true now.
Options
Highscope change
Overseas calling claim widens from impossible to enabled without the original restriction qualifier
In the knowledge base
Agency states Singapore does not permit VoIP calls from overseas, so overseas closers cannot place true local calls
Incoming
Agency's WhatsApp service sets up an entire phone ecosystem including WhatsApp Business and a Zoom phone dialler that bypasses VoIP restrictions in Singapore, enabling remote teams to call from a Singapore number
The client is hiring closers in Australia and has an open decision about hiring location. If the knowledge base says the restriction is bypassed without preserving what exactly is bypassed and under what conditions, the client may hire remotely on the strength of a capability claim that has load-bearing limits.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Mediumscope change
Ad audience widened from mothers to high-earning finance and tech professionals at named employers
In the knowledge base
Mothers identified as a target audience segment for the brand's advertising
Incoming
Ad targeting includes high-earning finance and technology professionals at companies such as Google, Goldman Sachs, McKinsey, Citibank and ByteDance
Both are recorded as targeting facts, so downstream writers may read the newer, broader segment as replacing the mothers segment, or may assume the named employers are clients rather than targeting criteria. Naming specific companies in creative also carries trademark and implied-endorsement risk.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Mediumunsupported
BlackRock Vice President title used in ad messaging with unresolved attribution
In the knowledge base
Founder Jennifer Ong's own career history includes a transition from BlackRock to a fashion startup
Incoming
A Vice President role at BlackRock is used in brand ad messaging as the pre-pivot role in a 'pivot without a pay cut' headline; source does not state whether the title is the founder's or a client's
The existing record confirms a BlackRock connection but never a seniority level, and never says whose. If this ships unresolved, live ads may claim VP seniority for the founder that nobody verified, or present a client outcome as the founder's story — either is a credibility risk on a headline claim.
Restates an approved fact without the qualifier that made it true.
Options
Mediumdrift
Motherhood audience segment paused for low lead quality while it remains on record as a target segment
In the knowledge base
Mothers identified as a target audience segment for the brand's advertising
Incoming
The motherhood-targeted ad set and its associated graphics were paused for producing consistently low-quality leads
Backward drift on a positioning fact. Left as-is, the knowledge base still authorises writers and media buyers to build mother-targeted messaging for a segment paid media has already switched off for poor lead quality — and the brand's origin story (founder designed her career around motherhood) makes that an easy segment to drift back into by accident.
Same measure moved backwards, which time does not explain.
Options
Mediumcontradiction
Webinar/step-two video length does not match either recorded webinar format
In the knowledge base
Runs an existing webinar as part of the funnel, in either a 20-minute or 60-minute format
Incoming
Step two of the funnel is a 75-minute video followed by calendar booking
The webinar length is quoted to prospects and used in nine months of performance analysis. If 75 minutes is the live asset, the 20/60-minute record is wrong and comparisons across the historical data are being made against the wrong asset.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Google ads is listed as one of five active funnels while also described as bypassing the funnel
In the knowledge base
Five active funnels are in operation, one each for meta ads, Google ads, Instagram, LinkedIn and organic (incoming, same session)
Incoming
Google Ads traffic goes directly to a booked call and does not pass through a funnel
Both statements arrived in the same session, so no passage of time explains the gap. Reporting on five funnels would attribute funnel-stage metrics to a channel that has no funnel steps, and the opt-in form count per channel would be wrong.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Organic is listed as an active funnel while website CTAs are said to send organic visitors straight to a booked call
In the knowledge base
Five active funnels are in operation, one each for meta ads, Google ads, Instagram, LinkedIn and organic (incoming, same session)
Incoming
Most calls-to-action on the website send organic visitors straight to a booked call, with a free webinar available somewhere on the site
Same-session statements that cannot both describe the current organic path. Attribution counts for organic (47 CRM contacts) depend on which route is live.
Two statements that cannot both be true now.
Options
Mediumunsupported
14% lead variance presented as an industry standard without a source
In the knowledge base
—
Incoming
An anticipated lead variance of 14% is treated as the industry standard, attributed to cookie tracking limitations and iOS 14
A precise figure attributed to 'industry standard' will be quoted back to the client to explain reporting gaps. If nobody can name the source, the agency is asserting a benchmark it cannot support.
Restates an approved fact without the qualifier that made it true.
Options
Mediumcontradiction
Sales manager credited with building GoHighLevel assets is reported to have left the company
In the knowledge base
Also holds a GoHighLevel account in which the sales manager created new calendars and funnels
Incoming
The sales manager who set up the existing Slack channel has left the company, prompting a plan to create a new dedicated Slack channel
A departed owner of the GoHighLevel account and Slack channel means access, admin rights and the planned validation walkthrough before shutdown may all be blocked — and the same access loss already happened with the previous funnel web system.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Agency position against minor creative variations sits against a plan to re-edit the same video at 1.5x speed
In the knowledge base
The agency's media buying position is that minor creative variations are not effective post-Andromeda
Incoming
Creative refresh approach under consideration is re-editing the same existing video in a different style or at 1.5x speed rather than re-recording
Both are incoming in the same batch and pull in opposite directions. Proceeding with speed-and-style re-edits under a stated position that such variations do not work wastes production time and muddies any read on creative performance.
Two statements that cannot both be true now.
Options
Mediumscope change
Founder-story creative moves from bottom-of-funnel placement to a top-of-funnel A/B test
In the knowledge base
Founder-story creative and objection-handling creative are used for bottom-of-funnel ad targeting
Incoming
Ad structure being planned distinguishes top-of-funnel from middle- and bottom-of-funnel ads, with founder story run as an A/B test and client stories and testimonials proposed for mid- and bottom-funnel
The funnel-stage qualifier on founder-story creative is load-bearing for budget allocation and audience targeting. Silently reassigning it would put bottom-funnel creative in front of cold audiences and misread the resulting performance.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Mediumcontradiction
Salesable migration recorded as complete, incoming sets a target date for full setup next week
In the knowledge base
Website and funnel migration onto the Salesable platform is complete, with the funnel rebuilt as a 3-step structure
Incoming
The target timeline for full Salesable setup is early to mid next week, as early as Tuesday
'Complete' and 'targeted for next week' cannot both describe the same scope. Planning and any client-facing status report depends on knowing which components are actually live, especially with a domain contingency plan in play.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Facebook ads described as ready to switch on, versus being urgently rolled back to Salesable
In the knowledge base
Facebook ads are currently running the old creatives and are ready to be switched on against the new funnel once internal links are updated
Incoming
Facebook ads are being moved back to Salesable immediately so that new lead data stops accumulating in the inaccessible funnel web platform
The two describe opposite postures — an orderly pending switch versus an emergency rollback driven by a platform lockout. Acting on the stale version risks continuing to send paid traffic into a platform nobody can access, losing the lead data it generates.
Two statements that cannot both be true now.
Options
Mediumscope change
Migrated-contact count restated as an exact figure with a named source and destination
In the knowledge base
500 contacts were carried over in the recent migration batch
Incoming
505 contacts were migrated from the legacy funnel web system to Salesable
Resolved as a refinement rather than a conflict, but flagged because the boundaries tightened at the same time as the number: the incoming names the source system and destination where the existing record said only 'recent migration batch'. Confirm the two describe the same event before the exact figure is promoted, otherwise a second migration could be silently absorbed into the first.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Mediumcontradiction
Slack notifications recorded as active, incoming says legacy Slack notifications have stopped
In the knowledge base
Slack notifications are active for both form submissions and appointment bookings
Incoming
Slack notifications from the legacy funnel web system have stopped working; the team only sees calendar entries from email
During a migration with legacy access deliberately retained to catch stray leads, believing notifications are live when they are not means bookings arrive unseen. The existing record also notes the sales manager who built the Slack channel has left, which makes silent failure plausible.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Ban-free WhatsApp method claimed alongside advice that bans occur regardless
In the knowledge base
Agency has developed a method for WhatsApp/phone systems in Singapore with high deliverability and without account bans, cracked approximately two months before this meeting
Incoming
Agency advises that hiring location for setters and closers should not be decided based on phone system limitations, since bans occur at high volume regardless of location
One statement sells a solved problem, the other says the problem is unsolvable at volume. Both are agency assertions with no external verification. If the stronger version is repeated to the client or in marketing, it becomes an unqualified capability claim the agency's own advice undercuts.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Marketing emails reported stopped while the base records twice-weekly list sends as ongoing
In the knowledge base
An email funnel exists in addition to the five channel funnels, fed by generic emails sent to the entire mailing list twice a week
Incoming
Marketing emails have been stopped; the only emails currently sent are onboarding emails to existing clients
The email funnel is one of the recorded active channels. If sends have actually stopped, any performance analysis attributing results to it is measuring a dormant channel, and the 14-day welcome journey's delivery status becomes ambiguous too.
Two statements that cannot both be true now.
Options
Mediumcontradiction
GoHighLevel shutdown decision sits against a plan to set one up later
In the knowledge base
The GoHighLevel account is to be shut down after a validation walkthrough of the migration
Incoming
Plan is to consolidate onto Salesable first and only later consider setting up a client-owned GoHighLevel account when advanced integrations such as WhatsApp Business are needed
Read together these look like a reversal. They are probably reconcilable — the sales manager's existing account closes, a new client-owned one may open later — but if the distinction is not recorded, someone will either shut down the wrong thing or pay twice for overlapping platforms, directly against the founder's single-platform requirement.
Two statements that cannot both be true now.
Options
Mediumunsupported
Regulatory claim about Singapore VoIP asserted without support
In the knowledge base
—
Incoming
Agency states Singapore does not permit VoIP calls from overseas, so overseas closers cannot place true local calls
This is a claim about what the law permits, presented as settled fact, and it is the stated basis for a hardware purchase recommendation and for hiring-location discussion. If it is an operational observation rather than a regulatory position, decisions are being anchored to something unverified.
Restates an approved fact without the qualifier that made it true.
Options
Mediumcontradiction
Facebook ads recorded as currently running, and as paused for sales-team training
In the knowledge base
Facebook ads are currently running the old creatives and are ready to be switched on against the new funnel once internal links are updated
Incoming
Facebook Ads were paused to allow internal training of the new sales team
Current channel status drives spend reporting, the ROAS figure and whether the new funnel switch-on task is still live. If the base state is wrong, performance analysis and the next media-buying decision are both built on a false premise. An earlier, separate pause is already on record for the 20-minute funnel period, so this is not simply that fact restated.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Funnel described as driving to a live webinar, while the recorded funnel step is a 75-minute recorded video and live webinars are only planned to resume
In the knowledge base
Step two of the funnel is a 75-minute video followed by calendar booking (with 'Live webinars are planned to resume' and 'Monthly live webinar series, targeted to launch late September or early October')
Incoming
The marketing funnel drives traffic to a live webinar, after which prospects can book an appointment directly or be followed up with by the sales team
Live versus pre-recorded is a load-bearing qualifier: it changes ad copy and reminder automations, and promising a live webinar in ads when the funnel serves a recording is a claim the brand cannot honour. The launch window in the KB lands on or just after today (2026-09-16), so the two statements may describe adjacent periods rather than the same one.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Incoming describes the funnel as driving to a live webinar; the knowledge base describes a recorded webinar asset with a 75-minute video step and says live webinars are only planned to resume
In the knowledge base
Step two of the funnel is a 75-minute video followed by calendar booking; The decision was made to run the 90-minute webinar funnel for now rather than rebuilding the 20-minute funnel; Live webinars are planned to resume with automated reminder emails and WhatsApp reminders set up beforehand
Incoming
The marketing funnel drives traffic to a live webinar, after which prospects either book an appointment directly or are followed up with by the sales team
'Live webinar' and 'recorded 75-minute video' cannot both describe the current step two. If the wrong one propagates, ads and landing pages promise a live session prospects will not get, and the funnel-performance comparison between the 90-, 60- and 20-minute versions is analysed against the wrong format. The incoming batch appears to be a pre-engagement audit, so this may simply be an older state — but without a date, drift and contradiction are indistinguishable here.
Two statements that cannot both be true now.
Options
Mediumunsupported
Broad software and web app development expertise claimed on the basis of CRM porting work
In the knowledge base
Agency team structure on the account includes a media buyer, a client strategy and account lead, and a dev lead (Alexander Singh) supervising the porting work
Incoming
Agency has expertise in software and web app development
The verified evidence is a dev lead supervising CRM migration and manual funnel rebuilds. Restated as software and web app development capability, it could be used in agency positioning or a pitch deck to sell build work the knowledge base has no proof the agency has ever delivered.
Restates an approved fact without the qualifier that made it true.
Options
Mediumscope change
Generic automation services claim drops the platform and use-case qualifiers carried by every existing automation record
In the knowledge base
Agency uses HighLevel primarily for automations; agency email deliverability remediation covers dedicated IP, SPF and DMARC; agency can route data out of a tenant platform into another HighLevel account and run the automations there
Incoming
Agency provides automation services
Every existing automation fact is bounded by platform and purpose. An unqualified automation services claim invites clients to expect automation work the agency has not scoped, and it is the kind of normalisation that erases load-bearing qualifiers.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Mediumcontradiction
Sending domain given as mail.controlcareer.com while every other domain record uses controlaltcareer.com
In the knowledge base
Sending emails from a subdomain (e.g. mail.controlaltcareer.com) rather than the root domain is the recommended setup; all calendar links now run on the controlaltcareer.com domain
Incoming
Email sending is configured in the CRM with SPF and DMARC records in place, with a sender name of Jennifer and an underlying sending domain of mail.controlcareer.com
If the sending domain genuinely differs from the brand domain by a missing 'alt', SPF and DMARC alignment and domain reputation work are being applied to the wrong host, and deliverability remediation would silently fail. If it is a transcription error, propagating it into the knowledge base will mislead whoever configures DNS next.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Slack notifications recorded as active for bookings, but two bookings produced no Slack notification
In the knowledge base
Slack notifications are active for both form submissions and appointment bookings
Incoming
Two calls booked on the morning of the call did not appear in Slack and arrived under an unfamiliar calendar name ('career consultation' rather than '1-on-1 career consultation call - Zoom'), suggesting another calendar link is still live
The team workflow is recorded as depending on only two systems, the calendar and Slack. If a stray calendar link is bypassing both the notification and the source tracking, leads are arriving unattributed and possibly unworked — the exact failure the migration was meant to close.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Landing page treated as a targeted revision in one record and as a possible layout rebuild or reuse of the 20-minute page in another
In the knowledge base
The existing landing page is being revised against specific client comments rather than fully redesigned
Incoming
Options under consideration for the landing page are a layout/design change or reusing the 20-minute page structure changed to say 60 minutes
One record commits to minimal revision, the other opens a structural change. Since landing page changes are deliberately deferred to avoid confounding creative results, acting on the wrong record could invalidate the creative test window that is also on record.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Agency specialty stated as back-end work against an existing claim of software and web app development expertise, alongside broad creative capability records
In the knowledge base
Agency claims specialised expertise in software and web app development
Incoming
Agency identifies its specialty as back-end work
Specialty claims are positioning statements that end up in pitches and proposals. 'Back-end work' and 'software and web app development' point at different buyers, and both sit awkwardly beside records claiming an in-house creative team, content creation and ad creative production. An unresolved specialty claim produces inconsistent positioning across assets.
Two statements that cannot both be true now.
Options
Mediumscope change
Graphic creatives turned off campaign-wide, where the existing record pauses graphics only as part of the motherhood ad set
In the knowledge base
The motherhood-targeted ad set and its associated graphics were paused for producing consistently low-quality leads
Incoming
Graphic (non-video) ad creatives have been turned off and will not be used at the start of the new campaign
The existing pause is qualified to one ad set and one reason. The incoming drops that qualifier and applies to all graphic creatives. If merged, the knowledge base would record that graphics were abandoned for producing low-quality leads, which is a broader and unverified conclusion about a whole format.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Mediumunsupported
Forward-looking claim that manual audience targeting will not be available in 2027
In the knowledge base
Agency strategy proposal is to focus on AI-based targeting and creative diversity in alignment with Meta's Andromeda update
Incoming
Agency position is that manual audience targeting is no longer significant and will not be available as an option going into 2027
The first half restates an approved position; the second half is a prediction about Meta's product roadmap presented as fact. If it reaches a client deck or an ad, the brand is making an unverifiable platform claim it cannot substantiate, and the strategy rationale collapses if Meta retains manual targeting.
Restates an approved fact without the qualifier that made it true.
Options
Mediumcontradiction
Conflicting account of whether the client is consulted before changes are made
In the knowledge base
Agency's media buying working style is to inform the client of the plan and proceed unless the client objects
Incoming
Agency's working style is to make landing page changes first and inform the client afterwards, and to run such changes as split tests
One version gives the client a chance to object before a change ships; the other does not. Getting this wrong on a live landing page means unannounced changes to a page the client believes is fixed, and a trust problem that is expensive to repair.
Two statements that cannot both be true now.
Options
Mediumcontradiction
Agency states two different core specialisations
In the knowledge base
Agency identifies its specialty as back-end work
Incoming
Agency identifies its specialisation as paid ads, defined by acting immediately when it sees a winning signal
The speciality claim is used in positioning and proposals. If the knowledge base holds two different answers, outbound materials will describe the agency inconsistently and the client will not know what they are buying.
Two statements that cannot both be true now.
Options
Mediumscope change
Email list of 9,000 is referred to as a WhatsApp-reachable lead list
In the knowledge base
Existing customer/contact database of 9,000 email addresses
Incoming
WhatsApp reactivation of a 9,000-lead list
An email address is not a WhatsApp-reachable phone number. Treating the two as the same list silently assumes phone coverage across 9,000 contacts, which drives both the revenue projection and the sending ramp plan. If coverage is lower, the whole plan is built on a number that was never verified.
Same claim, boundaries moved. Reads like a rewording; behaves like a new promise.
Options
Mediumunsupported
Projected $10,000 single-day revenue from WhatsApp list reactivation is asserted without evidence
In the knowledge base
Existing customer/contact database of 9,000 email addresses
Incoming
Agency states WhatsApp reactivation of a 9,000-lead list could unlock around $10,000 in one day after roughly two weeks of sending
This is a forward-looking revenue figure attached to a real list size. If it enters the knowledge base as a fact rather than a projection, it can surface in client-facing materials as a promise the agency has not demonstrated for this list.
Restates an approved fact without the qualifier that made it true.
Options
Lowprecision loss
Founder script-editing restated without the filming qualifier
In the knowledge base
The founder edits and films the ad scripts herself
Incoming
Founder edits her own ad scripts and produced the shortlisted creative selection herself
Low consequence, recorded for the audit trail only. The existing record covers both editing and filming; the incoming drops filming. Keeping the existing statement preserves the fuller fact and prevents a future restatement from narrowing the founder's production role by attrition.
Options
Lowcontradiction
Agency audit says ad-level tracking granularity is missing; KB says ad and hook attribution is already done manually
In the knowledge base
Leads are tracked manually by opening Zoom calendar entries to identify which hook and which ad generated each appointment (plus per-funnel opt-in forms, Meta lead/schedule pixel events and the 'source channel' custom field)
Incoming
Agency assessment is that the client's current tracking lacks the granularity to identify which specific ads generate the most efficient appointments
If ad-level attribution already exists manually, a tracking build-out may duplicate work already in place; if it genuinely does not, the KB overstates current capability and reporting built on it will be wrong. Low severity because the two may be measuring different things — identifying the ad versus costing it per appointment.
Two statements that cannot both be true now.
Options
Lowunsupported
Cost per booking recorded with an acknowledgement that the data supporting it is missing
In the knowledge base
—
Incoming
Cost per booking is approximately $30 to $40, though the figure is not confirmed due to missing bookings data
A clean-looking $30–$40 figure will survive downstream compression while the 'not confirmed' caveat will not. This is the classic broken-telephone path into an unverified performance claim in a proposal.
Restates an approved fact without the qualifier that made it true.