Holiday opening hours disagree across a business’s listings

The problem

Customers may see conflicting regular or holiday hours across the website and public profiles.

Agent job

Compare each public listing against the approved schedule; distinguish regular hours from special dates; prepare exact correction drafts and an evidence matrix.

Expected output

Dated hours-consistency report with screenshots and ready-to-review correction checklist.

Why an agent / simpler alternative

Assessment

The agent can compare differently presented opening hours and reason about date-specific exceptions or overnight closing. A stable listing-management tool is better for ongoing synchronized updates. A human owner must supply the truth and approve corrections; public listings cannot establish it alone.

Setup requirements

Items

1. Owner-approved regular and special-hours schedule for named locations

2. Exact owner-supplied URLs, timezone and department distinctions

3. Read-only browser access or owner-provided dated screenshots

4. No profile login required for an audit-only pilot

Inputs and access

1. Name

   Owner-approved location and holiday schedule

   Source or owner

   Prospective consenting customer or specified official publisher

   Sensitivity

   Use synthetic, public or appropriately deidentified material; confirm actual sensitivity before work

   Permission needed

   Owner authorizes scoped access and processing; verify rights and retention before receiving files

2. Name

   Public URLs supplied by the owner

   Source or owner

   Prospective consenting customer or specified official publisher

   Sensitivity

   Use synthetic, public or appropriately deidentified material; confirm actual sensitivity before work

   Permission needed

   Owner authorizes scoped access and processing; verify rights and retention before receiving files

3. Name

   Screenshots or authorized exports of profile hours

   Source or owner

   Prospective consenting customer or specified official publisher

   Sensitivity

   Use synthetic, public or appropriately deidentified material; confirm actual sensitivity before work

   Permission needed

   Owner authorizes scoped access and processing; verify rights and retention before receiving files

Proposed steps

1. 1

   Confirm location identities, local timezone and approved regular/holiday hours.

   Expected output: Canonical schedule

   Approval gate: Owner resolves all conflicting internal schedules first.

2. 2

   List exact sources to check and distinguish public viewing from any account edit permissions.

   Expected output: Source and access register

   Approval gate: Do not sign in or request new permissions for a read-only audit.

3. 3

   Capture each visible listing with URL, timestamp and whether it shows regular or special hours.

   Expected output: Dated evidence matrix

   Approval gate: Unavailable pages are unknown, not automatically wrong.

4. 4

   Normalize overnight spans and department-specific exceptions; compare with the approved schedule.

   Expected output: Discrepancy ledger

   Approval gate: Do not infer holiday closures from national calendars.

5. 5

   Draft precise corrections and route each to the owner responsible for that source.

   Expected output: Correction checklist

   Approval gate: No live edit or third-party communication without approval.

6. 6

   Have the owner review the report and define any separately authorized correction/recheck scope.

   Expected output: Accepted audit with open items

   Approval gate: If edits are later authorized, verify visible state and report pending review honestly.

Synthetic output illustration — not an executed result

Synthetic

Yes

Executed

No

Text

SYNTHETIC: Location North, 24 December: owner schedule 09:00–14:00; website 09:00–18:00; profile special hours not visible. Action: draft website correction; profile status UNKNOWN. This is a made-up comparison, not a live listing audit.

Human approval boundaries

1. Owner confirms schedule and business identity; all live listing edits require explicit approval. No account creation or new permissions.

2. Human service provider reviews quality, scope and quoted fee; customer approves contract, delivery recipients and payment terms. Separately approve purchases, credentials, publication and external sends. No commitments or payments are made in this research.

Failure modes

1. Search results are stale or personalized

2. Overnight hours cross date boundaries

3. Different departments keep different hours

4. Public pages may be temporarily unavailable

Recovery and troubleshooting

Items

1. If search snippets conflict with the page, record both and prioritize a fresh direct-page check without claiming the snippet is fixed.

2. If a profile is inaccessible, ask for an owner-provided screenshot or mark it unchecked; do not bypass access controls.

3. If hours cross midnight, confirm the owner’s intended date convention before suggesting a correction.

Unexecuted validation plan

Sample setup

Use screenshots of synthetic listings for two locations with overnight hours and one special closure.

Acceptance checks

1. All supplied sources checked with timestamps

2. Distinguish unavailable from incorrect

3. Every correction maps to owner-approved schedule

Stop conditions

1. Stop if data authority or rights are unclear.

2. Stop if critical seeded failures are missed; do not claim readiness.

3. Stop if manual correction time exceeds the pilot effort budget without customer approval.

Executed

No

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

CAD

Items

1. Agent subscription/API usage: not quoted; verify current plan and commercial data terms.

2. Human intake, rights review, QA and revisions: unknown until timed pilot.

3. Storage, hosting, integration and payment-processing costs: excluded unless separately agreed.

4. Customer acquisition and support time: not measured.

Caveat

No margin or income estimate. Price hypotheses are editorial offer tests, not observed market rates; taxes, scope and effort require a real quote.

Proposed service concept — earnings not verified or guaranteed

Buyer

Independent retailer or small multi-location hospitality business

Deliverable

Dated hours-consistency report with screenshots and ready-to-review correction checklist.

Charging basis

One-off pre-holiday listing audit; optional separately approved correction assistance.

Acquisition channel

Permission-based discovery with existing professional contacts, referrals or an opt-in sample page; none executed.

Assumptions

1. Customer has this unresolved problem and values a reviewed deliverable above existing built-in alternatives.

2. A consenting pilot confirms data access, achievable quality and economically tolerable review time.

3. Provider can deliver within a written scope and supports the result.

Revenue guarantee

No

Canadian adaptation — proposed

Proposed Canadian pilot: confirm the actual province, location timezone, overnight conventions and owner-approved holiday dates; do not infer closures from a generic Canadian holiday list. Check English/French versions separately if present and keep location-specific exceptions. No claim that live Canadian listings were checked.

Limits

1. Original proposed plan; untested.

2. Problem and capability references are evidence of context only, not demonstrated end-to-end success, customer demand, willingness to pay or profitability.

3. Compatibility, workload, delivery effort and availability must be verified in a real authorized pilot.

4. Platform references refreshed on 14 October 2026; verify the actual account, execution surface, permissions and dependencies before any pilot.

Candidate platforms — compatibility untested

1. Name

   Claude (Cowork capabilities)

   Required capabilities

   1. Authorized browser research plus editable report creation; exact account/browser compatibility untested.

   Capability source urls

   1. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork

   2. https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   Claude Cowork

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.