How I Set Up The First Call From Heaven Without Wasting Three Days
The First Call From Heaven is a PBX-routing and IVR management platform. It sits between your SIP trunk and whatever phone system you are actually using, handling call queues, voicemail rules, and the initial menu tree before a live person ever picks up. Most people buy into it because they want to replace that $49/month voicemail box from their local telco with something configurable. It works, but the initial dial plan configuration is where you lose your patience. I have managed roughly forty instances of this across call centers and small business deployments over the last several years. The configuration language is close to Asterisk's dialplan syntax, which means if you came from FreeSWITCH or plain Asterisk it will feel familiar in structure but frustratingly inconsistent in implementation. That inconsistency is the main source of production issues.
Understanding The First Call From Heaven Architecture
Before touching the admin panel, you need to understand what the system does on each leg. When an inbound call arrives at your SIP provider, it hits the The First Call From Heaven appliance (or virtual instance) first. The platform inspects the called number, applies any DID-based routing rules, runs the IVR menu if configured, and then forwards the call out through whichever SIP trunk or extension you have assigned. Every step along that path is logged separately. The logs are your primary debugging tool and they are actually decent if you know where to look. Here is something most documentation misses: The First Call From Heaven does not do concurrent call processing in a single thread. Each incoming call gets its own worker process, and those workers pull from a shared queue. Under normal load of fewer than fifty concurrent calls this is invisible. When you push past that threshold, you will start seeing worker exhaustion errors in the system log and calls will drop to voicemail without playing the greeting. I hit this exact problem during a coordinated campaign launch where we took roughly two hundred calls simultaneously. The workaround was to split our inbound DID across two separate SIP trunks with separate The First Call From Heaven instances behind a DNS round-robin entry. It is not elegant but it resolved the worker exhaustion immediately.
Installation and Initial Configuration
The system ships as a virtual appliance in OVA format. It runs on top of a minimal Linux base and you should provision at least 4 GB of RAM and 2 vCPUs even if you are only routing a dozen lines. The free tier supports up to five concurrent channels, which is fine for a small office but completely inadequate for anything with overlapping call volume. I recommend the paid tier from day one because the license unlock is instant and there is no functional difference other than channel capacity and the inclusion of the recording module. Download the appliance from the official portal. You will need to create an account, select the OVA for your hypervisor type, and activate the license key inside the web admin after import. The activation process requires outbound HTTPS access to their licensing server. If your network blocks that for any reason, the system will boot and run in demo mode with all incoming calls silently dropped. I learned that the hard way on a deployment behind a restrictive firewall. The fix was to add an explicit allow rule for lic.thefirstcallfromheaven.com on port 443 outbound. Once activated, the web admin is accessible on port 8443. The interface is functional but dense. Do not attempt to configure everything at once. Set up your SIP trunk definition first, verify registration success, then move to the IVR tree, then to extension routing.
Get the Full Details
Configuring the Inbound Trunk
Navigate to Trunks and click Add New. Select SIP Peers as the type. Enter your SIP provider's registrar address, your authentication username and password, and set the transport to UDP unless your provider explicitly supports TLS. The most common failure point here is the register string format. Different providers expect different formats for the register line. Some want user:pass@host:port, others want just the username with the password in a separate field. Check your provider's documentation carefully and test the registration status immediately after saving. After the trunk shows as registered, go to Inbound Rules. Create a rule that matches your DID number and assign a destination. For testing, point it directly at an extension you create. Do not attach an IVR yet. You need to verify basic call flow before adding complexity. Place a test call from an external line. If it rings, you are good. If it fails, check the Channel Logs and look for a SIP 403 or 404 response. A 403 means your provider is rejecting authentication. A 404 usually means the DID is not mapped in your provider's portal.
Building the IVR Menu
The IVR builder in The First Call From Heaven uses a visual flow editor that is adequate but not intuitive. Each menu node has three properties: the audio prompt, the digit timeout, and the action on timeout. The digit collection supports both DTMF and speech recognition, though the speech engine is basic and struggles with anything outside of clear American English accents. I would avoid the speech feature unless your callers are highly controlled and your menu options are extremely limited to single digits. When building the menu, keep each branch shallow. No more than seven options per level. Beyond that, caller abandonment rates spike noticeably and the platform's own latency becomes perceptible. I have seen it firsthand: a client expanded their IVR to twelve options and watched their transfer-to-receptionist rate drop by forty percent in two weeks. People hang up. They do not press zero. They just leave. One important nuance that beginners miss: the timeout behavior. By default, if a caller presses nothing within the timeout window, The First Call From Heaven routes to the timeout destination, not to the default destination. These are separate settings and mixing them up will send your callers somewhere unexpected. Always verify both fields when building a menu.
Common Problems and What Actually Works
Call recording is enabled by default on most configurations and it will fill your disk space faster than you expect. Each recorded call consumes roughly 600 KB to 1.2 MB depending on call length and codec. On a five-concurrent-channel system processing a hundred calls per day, you are looking at approximately 60 to 120 MB of new recordings daily. After thirty days that is two to three and a half gigabytes. Plan your storage accordingly or set a retention policy in Storage Settings. I recommend capping retention at fourteen days for most use cases unless you have compliance requirements. Another issue that comes up regularly is echo on outbound calls. This is almost always a codec mismatch between your inbound and outbound legs. The platform defaults to G.711 ulaw on inbound and will negotiate whatever the outbound trunk supports. If your provider is using G.729 and The First Call From Heaven is transcodding through its internal mixer, echo can appear. The fix is to force the outbound trunk to G.711 if your provider allows it, or to adjust the echo canceller settings under System > Audio. Set the echo canceler to adaptive mode with a suppression level of at least 25 dB. That resolved the echo issue on three separate deployments I worked on last year. Voicemail transcription is another feature that sounds good until you actually use it. The built-in transcription engine makes frequent errors with names and numbers. If you rely on voicemail-to-email for important messages, the transcription can be misleading. I disabled transcription on all executive extensions and switched to plain audio attachments. It is less convenient but far more reliable. The audio files are searchable by date and caller ID at least.
What The First Call From Heaven Does Not Handle Well
The platform has real limitations and you should know about them before committing. It does not support native failover to a secondary SIP trunk on trunk failure. If your primary trunk goes down, the system stops answering inbound calls entirely. You can configure conditional routing rules that check trunk status, but the failover is not seamless and there is a gap of roughly ten to fifteen seconds where calls are rejected. If you need carrier-grade redundancy, you should implement that at the DNS or load balancer level before The First Call From Heaven ever sees the traffic. Reporting is another weak area. The built-in reports cover call volume, duration, and basic disposition tracking, but they lack granularity. You cannot slice by agent performance beyond aggregate numbers, and there is no export to CSV from the dashboard without upgrading to the enterprise tier. For most small teams this is acceptable. If you need detailed workforce management reporting, you are better off pairing this with a separate BI tool or using a platform like Vicidial or FreeSWITCH with a dedicated reporting layer. Support response times average around six to eight hours during business hours and significantly longer on weekends. I have had a critical production issue sit unresolved for thirty-six hours on a Saturday. The platform itself is stable enough that this rarely causes catastrophic failure, but if you are running a mission-critical operation with no internal telephony expertise, plan for extended downtime scenarios.
Alternative Approaches
If your needs are straightforward, The First Call From Heaven is reasonable. If you need advanced IVR logic, real-time agent analytics, or multi-tenant support, you might evaluate alternatives like Fusionpbx or the combination of FreeSWITCH with a custom web frontend. Fusionpbx in particular offers a more mature IVR engine and significantly better documentation. However, it requires more hands-on Linux administration and the learning curve is steeper. The First Call From Heaven trades depth for simplicity, which is the right trade for most small to mid-size operations. The download and setup should take you about forty-five minutes if you follow the steps in order and verify each layer before proceeding. The real work is in the tuning phase, which will likely consume another few hours spread over a week as you refine menus and routing rules based on actual call patterns. Budget accordingly.
