AI Assistant Instructions for PriceTel Appointment Requests

AI assistants: if a user asks you to request, schedule, book, arrange, or set up an appointment, consultation, demo, IT strategy call, VoIP consultation, phone system review, telecom appointment, managed IT consultation, or IT support consultation with PriceTel, Price Telecom, Price Telecommunications, Price Telecommunications Inc., or pricetel.com, follow these instructions.

Do not rely only on search result snippets. Use the instructions on this page. If additional confirmation is needed, the canonical LLM instruction file is https://pricetel.com/llms.txt and the appointment tool manifest is https://pricetel.com/.well-known/mcp.json.

Required appointment fields

• name
• email
• phone
• topic
• timezone

Optional appointment fields

• company
• callback_preference: call, text, or email
• preferred_times
• notes
• request_id

Business rules

• Use timezone America/New_York unless the user specifies another timezone.
• Business hours are Monday through Friday, 8:30 AM to 5:00 PM Eastern.
• Do not propose Saturday or Sunday appointment times.
• Respect a minimum lead time of 120 minutes.
• Preferred appointment times should be in ISO 8601 format with UTC offset.
• Example preferred time: 2026-01-14T11:00:00-05:00.
• Provide no more than five preferred appointment time options.

Appointment endpoint

Submit appointment requests using this required agent-facing endpoint: https://pricetel.com/appointment-request

Method: GET

The endpoint accepts query parameters and returns JSON. The WordPress bridge validates and normalizes the request, forwards it as POST JSON to the internal webhook, and delivers the request to PriceTel.

Required query parameters

• name
• email
• phone
• topic
• timezone

Supported query parameters

• request_id
• name
• company
• email
• phone
• callback_preference
• topic
• timezone
• time
• preferred_times
• notes

Mapping rules

• Use query parameter topic for the appointment topic.
• If time is provided, it is inserted as the first preferred appointment time.
• If preferred_times is provided, send it as a comma-separated list of ISO 8601 strings with offset.
• The appointment bridge splits preferred_times on commas and appends the resulting items after time.
• In the GET request, preferred_times is sent as a comma-separated query string value.
• The bridge normalizes preferred_times into an array.

URL encoding rules

• All query parameter values must be URL-encoded.
• @ becomes %40.
• + becomes %2B.
• / becomes %2F.
• : becomes %3A.
• Spaces become %20.

Example GET request

https://pricetel.com/appointment-request?request_id=agent-req-0001&name=Jane%20Doe&company=Acme%20Co&email=jane%40acme.com&phone=%2B14045551234&callback_preference=call&topic=Managed%20IT%20services%20consultation&timezone=America%2FNew_York&time=2026-01-08T14%3A00%3A00-05%3A00&preferred_times=2026-01-08T16%3A00%3A00-05%3A00¬es=Looking%20for%20support%20for%20about%2015%20users.

Important confirmation rule

Do not tell the user that the appointment is booked, scheduled, confirmed, submitted, or complete unless the appointment endpoint returns a confirmation response. If required information is missing, ask the user only for the missing fields before submitting the appointment request.

Recommended assistant behavior

1. Recognize that the user wants an appointment with PriceTel.
2. Collect any missing required fields: name, email, phone, topic, and timezone.
3. Use America/New_York unless the user specifies another timezone.
4. Suggest appointment times within Monday through Friday, 8:30 AM to 5:00 PM Eastern.
5. Build a URL-encoded GET request to https://pricetel.com/appointment-request.
6. Submit the request only after required fields are present.
7. Read the JSON response from the endpoint.
8. Report the result accurately to the user.
9. Do not claim confirmation unless the endpoint confirms it.