Request processing
Use the channels below for booking questions, corporate documentation, and stay requests. Requests are processed by category and timestamp. Email confirmation is sent when an email address is provided.
- Booking inquiry: date range, suite type, occupant count.
- Invoice request: company name, billing address, tax identifiers if applicable.
- Late arrival notice: estimated arrival time, contact number.
- Accessibility request: feature type and required setup.
- Lost-and-found: item category, last known area, date range.
- Full name for correspondence and identification matching.
- Contact channel preference: email or phone.
- Request subject with one category.
- Date and time windows when relevant.
- Consent acknowledgement for form submission (Privacy Policy).
Personal data handling and retention terms are listed on the Privacy Policy page.
Overview
This page provides a documented request workflow. The form is intended for initial intake. Do not include payment card numbers in free-text fields.
- Form submission creates an intake entry.
- Category routing assigns the request type.
- Verification steps are requested if needed.
- Status updates are sent using the provided channel.
- Closure includes a summary when applicable.
- Only fields required for routing are collected.
- Free-text is intended for non-sensitive details.
- Attachments are not accepted through this form.
- Security incidents require phone escalation.
- Retention terms are stated in the Privacy Policy.
- One request category per submission.
- Dates must include timezone context if relevant.
- Corporate billing requires company identifiers.
- Accessibility requests should list feature type.
- Urgent matters should use phone contact.
Facilities
Contact-relevant facility notes for request routing and on-site actions.
| Topic | Processing |
|---|---|
| Check-in support | Identity check, deposit terms, access key issuance. |
| Extensions | Case-by-case. Requires availability and payment verification. |
| Late arrival | Notice logged with estimated time. Room holding depends on policy. |
| Incident intake | Initial report logged. Escalation path depends on category. |
| Lost-and-found | Search request logged. Matching requires item description and dates. |
- Invoice issuance on request, subject to account verification.
- Company fields: legal name, billing address, reference number.
- Tax fields provided when applicable and requested.
- Refund handling depends on booking channel and policy terms.
- Payment disputes require documented identifiers and timestamps.
For privacy and retention terms, review Privacy Policy.
Location
The map is provided for routing. For step-by-step arrival guidance, use the Location page.
- Address: 100 Front St W, Toronto, ON.
- Reference node: Union Station.
- For rideshare, confirm the pick-up point label shown in the app.
- For deliveries, provide recipient name and contact number.
- For time-critical arrivals, include buffer time for downtown traffic.
Pros / Cons
This list describes contact workflow constraints and supported channels.
- Multiple channels: phone, email, form.
- Form fields aligned to routing requirements.
- Map embed supports routing without account sign-in.
- Privacy and cookie references available on dedicated pages.
- Request categories defined for consistent triage.
- Form does not accept attachments.
- Urgent matters may require phone escalation.
- Billing response depends on business hours.
- Some requests require verification steps.
- Third-party booking issues may require provider contact.
Contact form
Provide only information required for routing. Do not include payment card numbers. Submission indicates acknowledgement of the Privacy Policy.
| Channel | Details | Use |
|---|---|---|
| Phone | +1 (416) 555-0138 | Urgent matters, arrival changes |
| [email protected] | Documentation, confirmations | |
| Address | 100 Front St W, Toronto, ON | Routing and deliveries |
| Policy | Privacy, Cookies | Compliance review |