Phase 3: Technical & Operational Setup
The third phase of WeatherIt partner onboarding covers technical integration, with separate paths for Post-Booking Tool and API integration.
Phase 3 covers the technical setup required to offer WeatherIt to your customers. The path you follow depends on your chosen integration model.
Integration Paths
flowchart TB
A[Phase 3: Technical Setup] --> B{Integration<br/>Model?}
B -->|No Development| C[Post-Booking Tool]
B -->|Full Integration| D[API Integration]
C --> E[Placement<br/>Configuration]
D --> F[Development &<br/>Testing]
style A fill:#e8f5e9
style B fill:#fff4e1
style C fill:#e1f5ff
style D fill:#f3e5f5
style E fill:#e1f5ff
style F fill:#f3e5f5
Path A: Post-Booking Tool
If you're using the Post-Booking Tool (hosted by WeatherIt, no development required):
A1. Placement of WeatherIt Offer
| Task | Description | Status |
|---|---|---|
| Email placement | Link added to confirmation emails | ☐ |
| Portal placement | Link added to customer portal/account | ☐ |
| Website placement | Agreed position on website | ☐ |
| Timing confirmed | When customers see the offer | ☐ |
A2. Data Flow Confirmation
| Task | Description | Status |
|---|---|---|
| Booking data | What data is shared (if any) | ☐ |
| Customer handoff | How customers transition to WeatherIt | ☐ |
| Return journey | How customers return after purchase | ☐ |
No Technical Development Required
The Post-Booking Tool requires no technical development. Configuration focuses on placement and customer journey.
Path B: API Integration
If you're using API integration (embedded in your booking flow):
B1. Technical Discovery
| Task | Description | Status |
|---|---|---|
| Booking flow mapped | Customer journey documented | ☐ |
| Data fields confirmed | Required data identified | ☐ |
| Trigger configuration | Aligned to your products | ☐ |
| Integration point | Where WeatherIt appears in flow | ☐ |
B2. Integration Development
| Task | Description | Status |
|---|---|---|
| API implementation | Integration code developed | ☐ |
| Sandbox testing | Testing against sandbox environment | ☐ |
| Error handling | Error scenarios tested | ☐ |
| Edge cases | Unusual scenarios handled | ☐ |
B3. Production Readiness
| Task | Description | Status |
|---|---|---|
| Monitoring | Production monitoring in place | ☐ |
| Incident contacts | Response contacts confirmed | ☐ |
| Go-live plan | Launch approach agreed | ☐ |
| Rollback plan | Fallback procedure documented | ☐ |
Technical Resources
Detailed technical documentation is available in the Technical Integration Guide. This covers API endpoints, authentication, webhooks, and more.
Both Paths: Final Validation
Regardless of integration model, confirm:
flowchart LR
subgraph Validation["Final Validation"]
direction TB
A["Customer journey<br/>works end-to-end"]
B["Data flows<br/>correctly"]
C["Messaging is<br/>consistent"]
D["Support processes<br/>are ready"]
end
style A fill:#e8f5e9
style B fill:#e8f5e9
style C fill:#e8f5e9
style D fill:#e8f5e9
Phase 3 Completion Criteria
Post-Booking Tool Path
| Item | Status |
|---|---|
| Placement locations agreed | ☐ |
| Links configured | ☐ |
| Customer journey validated | ☐ |
| Data flow confirmed | ☐ |
API Integration Path
| Item | Status |
|---|---|
| Technical discovery complete | ☐ |
| API implementation complete | ☐ |
| Sandbox testing passed | ☐ |
| Error handling verified | ☐ |
| Production readiness confirmed | ☐ |
| Monitoring in place | ☐ |
| WeatherIt confirms readiness | ☐ |
Test thoroughly before going live. Technical validation prevents customer-facing issues at launch.
Updated 8 months ago