Skej allows users to define advanced behavioral logic through Custom Instructions and date-bound Temporary Instructions.
These features give you flexible control over how Skej schedules beyond standard availability settings.
This article explains:
What Custom Instructions are
How they differ from core settings
How Temporary (date-bound) Instructions work
Best practices for predictable behavior
1. What Are Custom Instructions?
Custom Instructions allow you to define nuanced scheduling logic using natural language.
Examples:
“Don’t schedule Fridays unless it’s the only time available.”
“Always prefer mornings for internal meetings.”
“If I tell you to offer times starting at a future date, never offer times before that date.”
These instructions act as supplemental logic layered on top of your configured availability.
They influence how Skej proposes and negotiates times, but they do not replace your core settings.
2. How Custom Instructions Work
Custom Instructions:
Are global (apply to all scheduling interactions)
Are evaluated every time Skej processes a request
Add behavioral guidance to scheduling decisions
They do not:
Override hard availability constraints
Modify buffers, caps, or scheduling windows directly
Permanently alter your system settings
Automatically scope themselves to specific contacts
Think of them as interpretive logic, not configuration toggles.
You can access Instructions in your dashboard, by clicking Instructions in the left side bar, or clicking this link if already logged in.
3. Temporary (Date-Bound) Instructions
Skej also supports Temporary Instructions that apply only during a defined time window.
Example:
“I’m traveling to London the first two weeks of March. Only book me on London time.”
When creating a temporary instruction, you can:
Select a start date
Select an end date
Define behavior that applies only within that range
Once the date window expires, the instruction automatically stops applying.
This is ideal for:
Travel
Temporary schedule shifts
Event-heavy periods
Seasonal availability adjustments
Temporary Instructions provide flexibility without permanently altering your global scheduling logic.
4. Contact-Specific Instructions
Avoid including instructions that reference or apply to specific people, such as:
“Always prioritize John.”
“Never offer late afternoons to Sarah.”
Important:
Custom Instructions are evaluated globally — not automatically scoped to a single contact.
This means:
The logic will be read for every meeting.
Overlapping or conflicting person-specific rules can create unpredictable behavior.
Complex layering can reduce clarity.
Best practice:
Keep Custom Instructions general.
5. How Custom Instructions Interact With Core Settings
Core settings define the structural boundaries of your availability. These include:
Buffers
Meeting caps
Scheduling windows
Time-of-day rules
Minimum notice requirements
Custom and Temporary Instructions operate as behavioral guidance layered on top of these rules. In most cases:
Core settings define what is allowed.
Custom instructions influence how Skej chooses within what is allowed.
For example:
If your scheduling window ends at 5pm, a custom instruction cannot extend it to 7pm.
If multiple time slots are available, a custom instruction can influence which ones are preferred.
Avoid Conflicting Logic
Because Custom Instructions are flexible and expressive, conflicts can occur when:
An instruction contradicts a core setting.
Multiple custom instructions overlap.
A temporary instruction conflicts with a global one.
When conflicts exist, Skej attempts to reconcile them logically — but behavior may not always align with user expectations. Best practice:
Keep core settings clean and structural.
Use custom instructions for preference guidance, not structural overrides.
Avoid layering multiple rules that contradict each other.
6. Important Considerations
Because Custom Instructions are open-ended and expressive:
They are not pre-structured toggles.
They may not behave perfectly on the first attempt.
Edge cases can occur depending on phrasing.
Conflicting instructions may reduce predictability.
Custom Instructions should be treated as evolving logic.
7. Recommended Workflow
When adding or modifying a Custom or Temporary Instruction:
Keep wording clear and specific.
Avoid stacking too many layered rules.
Run a simple test scheduling request.
Confirm behavior matches expectations.
Refine wording if needed.
Small adjustments in phrasing can materially change behavior.
8. Design Philosophy
Skej is autonomous, but operates within defined system boundaries. Custom Instructions expand flexibility without compromising:
Predictability
Visibility
Enterprise safety
Configuration control
They allow advanced personalization while preserving stable system behavior.
Summary
Custom Instructions give you expressive scheduling control.
Temporary Instructions allow date-bound flexibility.
Used thoughtfully, they significantly increase Skej’s intelligence and adaptability — without introducing hidden configuration changes.