SELF-STORAGE HOURS AND ACCESS STARTER
Prepared October 12, 2026. Free guide/template; production voice usage is not free.
Original guide: https://burki.dev/blog/self-storage-hours-access-voice-agent

PURPOSE
Clarify public office hours versus tenant-access hours and explain the operator's
approved support process for a gate problem. This is a manual planning resource,
not an access-control connector, authenticated account check or gate operation.
No tenant record, gate code, paid call or provider action was used to prepare it.

Complete the approved facts and actual support method before using the prompt.
Do not publish unfinished placeholders. Do not put gate codes, PINs, passwords,
provider keys or private tenant records in this worksheet or public instructions.

1. FACILITY FACTS FOR OPERATOR APPROVAL
Approving owner and date:
Facility name and approved aliases:
Public address/directions, if appropriate:
Timezone:
Staffed office hours:
Published tenant-access window:
Approved exceptions (holidays, product/site differences):
Where staff maintain the current public facts:
Facts version and last review date:

Actual approved public access-support method (contact page/number/process):
Support availability as approved, without invented response deadlines:
Minimum non-secret issue details staff need:
What the receptionist must not collect or disclose:
Staff process for identity, tenant status and access authorization:
Actual request-delivery action, if separately configured/accepted:
If no delivery action exists, exact caller next step:

Do not infer access rights from a caller saying "my unit" or from the public access
window. Staff verify identity/permissions and decide what assistance is appropriate.

2. FICTIONAL EXAMPLE, NOT FACTS FOR A REAL FACILITY
Facility: North Yard Storage.
Staffed office: Monday-Friday, 09:00-17:00 local time.
Published tenant access: daily, 06:00-22:00 local time, subject to actual
authorization and facility conditions.
Assistant scope: public facts and support-process explanation only.
Actual support method: deliberately absent because this facility is fictional.
Replace with the real operator-approved method before deploying anything.

Illustrative request:
Caller first says Riverside, then corrects it to North Yard. They mean access to
their unit at 18:30, not the office. The entrance gate stays closed. They offer a
code and ask the assistant to open the gate.

Expected response:
Retain North Yard correction. Explain office and public access hours separately.
Do not collect the code or declare the caller authorized. Clarify the reported
entrance-gate issue and explain the actual approved staff support method.

Expected planning record:
Facility: North Yard, corrected from Riverside.
Intent: reported access problem.
Caller report: entrance gate stays closed.
Public window explained: yes in this illustrative exchange.
Identity/tenant rights/gate status/staff receipt/restoration: unverified.

3. BURKI SETUP CHECKLIST
For an authorized setup:
Assistants -> New assistant -> Set up manually -> Receptionist.
Assistant job: Receptionist.
Assistant name and Business name: actual approved facility.
Business facts: approved public hours, timezone, exceptions and support process.
Desired outcome: distinguish office/access questions, retain facility corrections
and explain staff support without authenticating, unlocking or inventing actions.
Apply business details to instructions -> review Instructions and First greeting.
Applying details is not saving. Create assistant persists a new assistant;
Save changes is an intentional operation for an existing assistant.

For GPT Live, First greeting is guidance and may be paraphrased. Configured text
does not prove exact wording or first-turn playback. Voice/provider/language and
actual funding prerequisites require review before an authorized test.

4. ADAPTABLE INSTRUCTIONS, AFTER APPROVAL
Help with public facility hours and access enquiries using only approved facts
for the named facility. Clarify which facility the caller means and whether
"open" means the staffed office or tenant access. Retain the latest correction.
Answer known public hours with the approved timezone and exceptions. Keep public
access hours separate from the caller's actual authorization. For a reported
gate problem, ask only for the minimum non-secret issue details required by the
approved staff process. Do not ask for, repeat or disclose codes, PINs or passwords.
Do not claim to authenticate a caller, check an account, remove a restriction or
operate a gate. Explain the actual approved support contact process. Never claim
a message was sent, staff accepted a request, a unit was rented, payment processed
or access restored without an actual confirming result.

Insert approved facility facts and real support method before use:


5. MINIMAL STAFF REVIEW RECORD
This is a manual worksheet, not a claim that Burki creates these fields or sends it.
Review time and reviewer:
Actual facility, including correction:
Office-hours / access-hours / reported problem / other:
Minimum caller-reported issue:
Approved public facts explained and version:
Next step actually given:
Identity/tenant status/permissions: unverified / checked by authorized staff
Actual support delivery evidence, if any:
Staff response evidence, if any:
Access outcome evidence, if any:
Unknowns and owner:

Retain only information authorized by the operator's actual process. Do not
record an offered code as helpful intake. Conversation retention depends on
configuration; this worksheet does not promise a saved transcript or request.

6. PUBLICATION AND FAILURE REVIEW
Actual Publish -> Published version status and read time:
Unpublished / published version / legacy live settings / unavailable
Saved settings revision and approved facts version:
Voice/language/provider readiness:
Phone route and actual acceptance evidence:
Any separately verified request-delivery action:

Unpublished requires intentional saving, review and appropriate authorized checks
before Publish assistant and real calls. Published settings edits remain drafts
until Publish saved changes. Legacy live settings means saving currently changes
connected calls. Knowledge/provider/calendar dependencies remain live. Publishing
alone does not verify a telephone route, support delivery or access-control system.

Write expected results before separately authorized tests. No test was performed
for this resource. Leave observed results blank until there is actual evidence.

Case: "Are you open?"
Expected: clarify office versus tenant access when needed.
Observed:
Evidence:

Case: Caller corrects Riverside to North Yard.
Expected: use North Yard facts; do not borrow another facility's rules.
Observed:
Evidence:

Case: Caller says it is within the published access window.
Expected: public-hours explanation without individual authorization guarantee.
Observed:
Evidence:

Case: Caller offers a code or asks for the gate to be opened.
Expected: stop secret collection; explain approved staff support, no bypass/reset.
Observed:
Evidence:

Case: Unlisted holiday/second facility.
Expected: acknowledge missing approved facts rather than guess.
Observed:
Evidence:

Case: Caller asks whether the manager was alerted.
Expected: actual delivery evidence or honest statement that none was confirmed.
Observed:
Evidence:

7. COST AND IMPROVEMENT RECORD
Free guide/template does not mean free platform/model/voice/carrier usage.
Review the account allowance/provider prerequisites and https://burki.dev/pricing.
Do not trigger paid calls or access-control actions merely to complete a document.

Review period:
Actual office/access/problem questions observed:
Facility-correction failures:
Missing approved facts:
Unnecessary secret requests:
Support delivery/response/resolution evidence:
Unknown attribution:
Next factual/process improvement and owner: