Parent and Child Account Relationship

The present disclosure involves enabling a parent and child account relationship. One example method includes identifying a child account associated with a parent account, the parent account including a monetary amount, the child account being different than the parent account; identifying a communication associated with the child account; transferring at least a portion of the monetary amount from the parent account to the child account after identifying the communication associated with the child account; and debiting the portion of the monetary amount in the child account for charges associated with the communication.

TECHNICAL FIELD

The present application generally relates to communications, and more specifically, to a relationship between parent and child accounts in which a portion of the parent balance is transferred from the parent account to the child account when the child account is used for a communication.

BACKGROUND

Communication services are generally provided to holders of accounts. In some cases, the accounts are associated with a balance or monetary value that is used to pay for any charges accrued while using the communication service. Generally, the balance associated with the account will be debited for the accrued charges, and if the account does not have sufficient funds to cover additional charges, the communication service will be terminated.

SUMMARY

The present disclosure involves systems, software, and computer implemented methods for enabling a parent and child account relationship. One computer-implemented method includes identifying a child account associated with a parent account, the parent account including a monetary amount, the child account being different than the parent account; identifying a communication associated with the child account; transferring at least a portion of the monetary amount from the parent account to the child account after identifying the communication associated with the child account; and debiting the portion of the monetary amount in the child account for charges associated with the communication.

Prepaid communication services generally apply charges accrued during a communication, such as a telephone call, to an account associated with the communication. The account may be associated with a personal identification number (PIN) and used by the account holder to identify the account. Generally, when the balance on a prepaid account is exhausted, any associated communications will end. Furthermore, each account is generally independent from other accounts, and its balance is kept separate from the balances of other accounts.

In some cases, it may be advantageous to allow an account to share the balance of a “parent account.” For example, a business may wish to maintain a single balance or credit limit for all of its long distance usage to efficiently manage cost but issue a separate account to each employee to track individual usage. One possible approach would be to associate multiple PINs to a single account, and allow multiple simultaneous communications to occur. One problem with this approach is the inability to reliably indicate an amount of the communication service that may be obtained using the balance. For example, if a second PIN is used to access the account while a communication using a first PIN is active, the balance on the account will now be depleted at a different rate as compared to when only one pin is actively used thereby rendering any estimate service usage remaining associated with the first PIN inaccurate. This may be important for prepaid services where an amount of time based on the balance is announced to a user at the beginning of a communication (e.g., a prepaid phone call). The present disclosure describes various techniques for coordinating simultaneous communications sharing a balance through a parent/child paradigm that controls and monitors transfer of funds between accounts.

DETAILED DESCRIPTION

The present application generally relates to communications, and more specifically to a relationship between parent and child accounts in which a portion of the parent balance is transferred from the parent account to the child account when the child account is used for a communication.

Prepaid communications services generally apply charges accrued during a communication, such as a telephone call, to an account associated with the communication. The account may be associated with a personal identification number (PIN) and used by the account holder to identify the account. Generally, when the balance on a prepaid account is exhausted, any associated communications will end. Further, each account is generally independent from other accounts, and its balance is kept separate from the balances of other accounts.

In some cases, it may be advantageous to allow an account to share the balance of a “parent account.” For example, a business may wish to maintain a single balance for all its long distance usage, but issue a separate account to each employee so individual usage may be tracked. One possible approach would be to associate multiple PINS to a single account, and allow multiple simultaneous communications to occur. One problem with this approach is the inability to reliably indicate an amount of the communication service that may be obtained using the balance. For example, if a second PIN is used to access the account while a communication using a first PIN is active, the balance will now be depleted at a different rate as compared to when only one pin is actively used thereby rendering any estimate service usage remaining associated with the first PIN inaccurate. This may be important for prepaid services where an amount of time based on the balance is announced to a user at the beginning of a communication (e.g., a prepaid phone call).

In some implementations, the present solution may allow for simultaneous access by multiple users to an account balance while avoiding the problems of the approaches discussed above. The solution may involve designating an account including a balance as a parent account, and designating other accounts to be used to access the balance as child accounts. When a communication is initiated using one of the child accounts, a portion of the parent account balance may be transferred to the child account, and added to the balance associated with the child. The communication then proceeds, and any accrued charges are debited from the child account balance. When the communication ends, the child account balance may be transferred back to the parent account, such that the child account is left with a zero or nominal balance at the conclusion of the communication.

In some implementations, the present solution may be used in a prepaid telecommunications scenario. For example, a caller may initiate a phone call to a prepaid telecommunications system and enter a PIN corresponding to a child account. A corresponding parent account for the child account may be identified. A certain amount of funds may then be transferred to the child account from the parent account for use during the phone call. The amount of funds may then be announced to the caller. The caller may then place a call to a destination. During the call, charges may be debited from the child account balance. When the caller is finished with the call, the caller may hang up to end the call. When the call ends, the remaining balance on the child account may be automatically transferred back to the parent account.

In some implementations, if the child account's balance is exhausted during the communication, an additional transfer of funds from the parent account to the child account may be performed. Referring again to the prepaid telecommunications example, if the child account's balance drops below a certain threshold during the phone call due to the accrued charges for the call being debited from the balance, an additional amount may be transferred from the parent account for use on the call. This avoids the phone call ending due to the child account having insufficient funds to continue the phone call.

The present solution includes several advantages. First, the solution alleviates many issues related to coordinating multiple communications debiting a balance at once, allowing for a simple and elegant implementation of accounting logic. Second, the solution allows tracking, management, and configuration of individual accounts while allowing the accounts to pull from a common parent account balance. For example, each child account may be configured with different preferences related to the communications services. The preferences may include, but are not limited to, separate conference bridges using the same parent account, accountability/tracking reports, speed dial configurations, or any other suitable preferences. In addition, because recharges for the child accounts may occur via the parent account, credit card configurations related to recharge may be stored in the parent account, and need not be configured for each individual child account.

FIG. 1shows an example environment100for enabling a parent-child account relationship. The example environment100includes a call processing server102, a client140, one or more network switches132, a subscriber150, and a destination152. In the illustrated implementation, a network130connects the various components.

In operation, subscriber150may initiate a communication to one of the one or more network switches132via the network130. Subscriber150may enter account information to identify the account to charge for the associated communication. The indication may be sent from the network switches132to call processing server102, where it may be interpreted by the account manager108. The account manager108may consult the database120determine whether the account denoted by the account information is a child account associated with a parent account. If the account information is associated with a child account, the account manager108may transfer a certain amount of funds from the parent account associated with the child account to be used for the present communication. In some implementations, the amount to transfer may be preconfigured, or the amount may be computed based on attributes of the communication, such as the intended destination, the rate associated with the communication, or other attributes.

Once the funds are transferred from the parent account to the child account, the account manager108may indicate to the subscriber150the balance now associated with the child account. The communication requested by the subscriber150may then proceed. When the communication finishes, the account manager108may receive an indication that the communication has ended. The account manager108may then transfer any remaining funds from the child account to the parent account, such that the child account is left with a nominal or zero balance at the conclusion of the communication.

In some cases, the initial amount transferred from the parent account to the child account may not be sufficient for the entire communication. If the transferred balance is completely used and the communication is still ongoing, the account manager108may transfer additional funds from the parent account to the child account for use by the communication. In some implementations, this “recharge” functionality may be executed when the balance associated with the child account reaches a certain threshold, when the amount of time remaining for the communication based on the balance of the child account reaches a certain threshold, or any other suitable condition.

As shown inFIG. 1, the environment100includes a call processing server102. In the depicted implementation, the call processing server102is a data processing apparatus that may include various components for providing communications service, including an interface104, a processor106, and an account manager108.

The interface104may be used by the call processing server102for communicating with other systems in a distributed environment—including within the environment100—connected to the network130; for example, the client140, as well as other systems communicably coupled to the network130(not illustrated). Generally, the interface104comprises logic encoded in software and/or hardware in a suitable combination and operable to communicate with the network130. More specifically, the interface104may comprise software supporting one or more communication protocols associated with communications such that the network130or interface's hardware is operable to communicate physical signals within and outside of the illustrated environment100.

The call processing server102may include a processor106. In some cases, the processor106directs the operation of the other components of the call processing server102by executing the software instructions making up these various components. In some cases, the processor106may include multiple physical central processing units (CPUs) which may be contained inside a single chassis or distributed across multiple computers and connected via a network or backplane. In some cases, the processor106may be a general purpose processor such as those produced by INTEL, AMD, HP, ARM, APPLE, or any other suitable processor. The processor106may also be a custom application specific integrated circuit (ASIC) or field programmable gate array (FPGA) specifically adapted to the present application.

In the illustrated implementation, call processing server102includes an account manager108. In some implementations, the account manager may be operable to perform accounting operations during a communication handled by the call processing server102. For example, if the subscriber150makes a telephone call to the destination152through one of the one or more network switches132, the telephone call will accrue a certain amount of charges based on how the subscriber's account is configured. The account manager108may keep track of the charges accrued during the communication, and debit a balance associated with the subscriber's account as the communication proceeds. In some implementations, the account manager108may be a software program or collection of software programs running on the call processing server102. The account manager108may also be a software program running on a separate server from the call processing server communicating with the call processing server102via the network130. The account manager108may also be implemented in hardware, or a combination of hardware and software.

As shown, the account manager108may include a relationship manager110. In some implementations, the relationship manager110may be operable to determine a relationship between a child account and a parent account. The relationship manager110may make this determination by consulting the database120, specifically the account relationships126. For example, if the subscriber150enters an account number of “12345” at the beginning of the communication, the relationship manager110may consult the database to determine whether the account associated with account number “12345” has an associated parent account. In some implementations, the relationship manager110may determine whether an account is associated with the parent account by querying the database120using Structured Query Language (SQL), or any other suitable query language supported by the database120.

In some implementations, the relationship manager110may enforce characteristics on the parent and child accounts stored in the database120. For example, a parent account may not be permitted to be used to initiate communications in some cases. In such a case, the relationship manager110may detect that the provided account is a parent account, and may reject the request to start the communication.

The account manager108may also include a balance manager112. In operation, the balance manager112may transfer a portion of the balance from a parent account to a child account at the beginning of the communication associated with the child account. For example, the communication is to be initiated on child account “12345,” the balance manager112may reduce the balance with a parent account by a configured amount, and increase the balance associated with the child account by that same amount. In some implementations, the balance manager112may insert a transaction record into a table in the database120to indicate that such transfer has been made. In some cases, the balance manager112may consult a configuration table to determine the amount to transfer from the parent account to the child account. The balance manager112may also determine the amount to transfer from the parent account to the child account based on characteristics associated with the requested communication. For example, if the requested communication has an associated rate of ten cents a minute, the balance manager112may be configured to provide the child account with sufficient funds for a ten minute communication. In such a case, the balance manager112may transfer one dollar (sufficient funds for ten minutes of talk time at a ten cents per minute rate) from the parent account to the child account.

In some implementations, the balance manager112may also be operable to transfer any remaining funds from the child account to the parent account when a communication ends. For example, the communication associated with a rate of ten cents per minute ends after nine minutes, a balance of ten cents will be left on the child account. The balance manager112may transfer this remaining ten cents from the child account to the parent account, such that the child account is left with a zero balance at the end of the communication. In some implementations, the child account may be left with a nominal balance (e.g. one cent) at the end of the communication. The balance manager112may also insert a transaction record into the database120to indicate that this end of call transfer has occurred.

As shown, the account manager108also includes a recharge manager114. The recharge manager114may be operable to detect the child account associated with the communication has had its balance fall below a configured threshold. The recharge manager114may then initiate a transfer of funds from the parent account to the child account for use in the associated communication. For example, if a child account is associated with a communication with a rate of ten cents per minute, and the balance of the child account is ten cents, the recharge manager114may detect that the child account has one minute of talk time remaining. If this amount of talk time is below a configured threshold, the recharge manager may transfer a configured amount of funds from the parent account to the child account. For example, recharge manager114may debit the parent account by one dollar and add one dollar to the child account. The recharge manager may perform this process multiple times during a given communication if the child account balance falls below the configured threshold multiple times—in some implementations, the recharge manager114may insert transaction record in the database120to indicate that a transfer has occurred from the parent to child.

The call processing server102may also include a memory107for storing a database120. The database120may include several different databases hosted on different servers connected via local area network or a public network such as the Internet. In such a configuration, the component databases of database120may be interconnected by a replication mechanism that keeps the component databases in sync. In some implementations, the component databases may be exact replicas of each other, while in other implementations only a portion of the databases may be replicated. The database120may be provided and managed by a database management system (DBMS) including, but not limited to, ORACLE, INFORMIX, DB2, SQL SERVER, MYSQL, POSTGRES, SQLITE, VERTICA, or any other suitable DBMS. In some cases, the various data items stored by database120may be stored in separate relational tables, while in other cases the data items may be stored in individual rows inside a table, in columns inside a table, across various tables, more than one data item in a single table, or in any other suitable configuration. The database120may also store additional configuration related to the other components of the call processing server102, which may access the database120to retrieve this information and the data items specifically described herein.

As shown, the database120may include one or more parent accounts122, and one or more child accounts124. In some implementations, the parent accounts122and the child accounts124may be included as records inside a single or multiple database tables. In some cases, the parent accounts122and the child accounts124may share a common structure or format, such that the two are differentiated by attributes stored in the table, or by attributes stored in another table. For example, a parent account122and a child account124may differ based on a type attribute that indicates that the parent account is a parent of the child account. In some cases, the parent accounts122and child accounts124are differentiated by the account relationships stored in the account relationships table126.

In some implementations, the parent accounts122may include one or more identifiers usually identifying the account, such as an account number or personal identification number (PIN). The parent accounts122may also include a balance associated with the account in some cases which may be stored as a numeric value indicating a monetary amount, such as amount of cents, dollars, or other monetary.

In some implementations, the database120may include child accounts124. In some cases, the child accounts124include information related to the account, such as a PIN, a balance, statistics related to the usage of the account, and other settings related to the account. In some cases, the child accounts124may include a type field that indicates that the child account124is a child account.

As shown, the database120also includes one or more account relationships126. In some implementations, the account relationships126may be rows inside a table separate from the parent accounts122and child accounts124. The account relationships126may include an indication of a parent account and associated child account. In some cases, the account relationships126may include a unique identifier for the parent account in the child account, such as an account number or PIN. Account relationships126may also include additional attributes or settings associated with the relationship, such as, for example, an amount associated with each transfer from the parent to child account, a recharge threshold indicating when to perform additional transfers from parent to the child account during a communication, an indication of an end of communication behavior associated with the relationship, or any other suitable attributes.

The environment100may also include one or more network switches132communicatively coupled to network130. In some cases, the network switches132may be standard telecom equipment used to connect time slots or ports together to complete telephone calls. The network switches132may also be voice over internet protocol (VOIP) equipment operable to service telephone calls originating and/or terminating to IP networks. The network switches132may be commercially available networking equipment including products manufactured by ALCATEL-LUCENT, CISCO, NORTEL, HP, STRATUS or any other suitable switching product. The network switches132may also include general purpose routers, multiplexers, gateways, or other equipment. In some cases, the network switches132may be controlled by the call processing server102via one or more APIs. The APIs may be standard protocols such as SIP or H.323, proprietary control protocols specific to the manufacturer of the network switch, or any other suitable API or combination of APIs.

The environment100may also include a subscriber150. In some cases, the subscriber150may be a person associated with one of the parent accounts122or the child accounts124. The subscriber150may access the call processing server102by an access number on an associated telephone. The subscriber150may also access the call processing server102by connecting to an IP address associated with the call processing server102or one of the network switches132. In some instances, the subscriber150may access the call processing server102or network switches132using a software application configured to communicate with these components. The call processing server102may provide a service to the subscriber150. For example, the call processing server102may provide a prepaid calling service to the subscriber150, in which the call processing server102prompts the subscriber150for an account number or PIN, prompts the subscriber150for a destination number to connect to, and then tracks the charges accrued for the talk time associated with the call and debits the balance of an associated account accordingly. In some cases, the call processing server102may interact with the one or more network switches132to connect subscriber150to a destination152. In some cases, destination152may be another subscriber of the call processing server102. The destination152may also be any telephone or other communications device, and may be identified by a destination entered by the subscriber150.

The environment100may also include a client140that includes a GUI142. The client may include an interface149, a processor144, a memory148and a client application146. The client140may be used by an administrator or a subscriber to access the call processing server102in order to view or change the various data items stored in database120, view or change reports generated from the data items in the database120, make calls or perform any other suitable function.

FIG. 2shows an example interaction200for enabling a parent-child account relationship. Example interaction200occurs between the subscriber150, the account manager108, and the database120described relative toFIG. 1. At202, subscriber150enters account information which is sent to the account manager108. In some implementations, the subscriber150may enter account information, such as account number or PIN, at the beginning of the communication to indicate the account to be charged for the communication. In some implementations, entering the account information may include typing the account number on a touchtone keypad of the telephone, speaking the account number into the telephone, or any other suitable mechanism for entering the account information. In some cases, the account information may be entered by the subscriber by performing an application programming interface (API) call to the call processing server102, or to another component within the environment100. Although the interaction200shows the subscriber150entering the account information directly into the account manager108, the account information may be forwarded from another component or components within the environment100to the account manager108.

At204, the account manager108looks up the account type of the account associated with the account information in the database120. In some implementations, the account manager108may issue an SQL query to the database120to lookup the account type associated with the account. In some cases, the account manager108may query an account record that includes the account type. The account manager108may also query a separate record from the account record, such as the account relationships126, in order to determine the account type.

At206, database120returns an indication that the type of account associated with the account information is a child account. In some cases, the account may be designated as a child account by the inclusion of a row associated with the account in the account relationships126. The account may also be indicated as a child account by a value in a type field in the account record.

At208, the account manager looks up the parent account for the account associated with the entered account information in the database120. In some implementations, looking up the parent account includes reading a parent account number from the account relationships126, and querying an account table for the parent account.

At210, the account manager108instructs a database to transfer an amount from the parent account to the child account. In some implementations, the account manager108may consult a separate configuration table or resource to determine the amount to transfer from the parent account to the child account. In some cases, the amount transferred may be based on a destination associated with the request of communication. For example, if the requested communication is associated with the destination of Vietnam, the communication may be associated with a higher rate than the communication associated with United States. In such a case, the account manager108may transfer a larger amount from the parent account to the child account for a communication associated with Vietnam than for a communication associated with United States. In some implementations, the amount to transfer is based on a rate associated with the communication. In some cases, the amount of transfer is based on a configuration associated with the relationship, or with the parent or child account.

At212, the account manager108indicates an amount remaining on the account to the subscriber150. In some implementations, the account manager may send a message to another component within the environment100instructing the component to indicate the amount remaining to the account subscriber. For example the account manager108may use an API to control an interactive voice response (IVR) to speak an amount in dollars and cents corresponding to the amount remaining on the child account. In some implementations, the account manager may return this amount remaining to the subscriber in response to an API call requesting initiation of the communication. At214, the communication requested by the subscriber150occurs. In some implementations, the communication occurring may include subscriber150having a telephone conversation with the destination152. The communication occurring may also include the subscriber150participating in a conference call with other subscribers. Communication occurring may also include subscriber150making a voice over IP (VOIP) call to a destination152over an IP network such as the Internet. The communication occurring may also include other types of electronic communication, such as email, file transfers, text messages, or any other suitable type of communication.

At216, subscriber150indicates to the account manager108that the communication has ended. As discussed previously, although the interaction200detects this indication is occurring directly between the subscriber150and the account manager108, the indication may be forwarded through many different components between the subscriber150and the account manager108. For example, the subscriber150may indicate the communication has ended by hanging up a telephone receiver at the end of the telephone call.

At218, the account manager108transfers an amount remaining on the child account to the parent account. In some implementations, the account manager108will transfer the entire remaining balance on the child account back to the parent account when the communication ends. In some cases, the account manager108may leave a nominal amount such as one cent on the child account at the conclusion of communication. The amount to be left on the child account at the end of the communication by the account manager108may be configured within the database120.

FIG. 3shows an example interface300for configuring a parent account. The example interface300includes a search type drop-down302, an account search box304, and a search button306. These components are operable to allow a user to enter an account number or PIN and search for information about that account by pressing the search button306.

The interface300also includes an account summary tab307to display information related to the selected account. The account summary tab307includes information related to the account retrieved in response to the search. The account summary307includes a PIN308, a PIN status310, a balance312, and a parent PIN indicator314. The parent PIN indicator314shows that the present PIN is a parent PIN by displaying the text “on”.

The interface300also includes an update tab315. A user of the interface300may use the update tab315to change attributes associated with all child accounts associated with the parent accounts. As shown, the update tab315includes a threshold type drop down box316, from which the user can select the type of threshold that should be used when transferring funds from the parent account to the child account. For example, the threshold type drop down box316indicates that a time threshold should be used, such that when a certain amount of time is remaining on the account, a transfer from the parent account to the child accounts should be initiated. For example, if the communication is active and the balance on the child account has dropped to a level where the communication may only continue for another minute, a transfer from the parent account to the child account may be initiated if this amount remaining is below the configured threshold. The update tab315also includes a threshold value318that may be used to set the threshold at which a transfer from the parent account of the child account will occur. The update tab315also includes a recharge amount field320into which the amount to be transferred from the parent account to the child account may be entered. To perform the update specified by the update tab315, the user may activate the update button321.

The example interface300also includes an add child PIN tab330. As shown, the add child PIN tab330includes a child PIN field322, a threshold type drop down324, a threshold value field326, and a recharge amount field328. Users of the interface300may use these fields to indicate a child account to be associated with the current parent account, as well as the attributes to be associated with that child account. The add child PIN tab330also includes an add child button332that the user may activate in order to add the specified account as a child and set the specified attributes.

FIG. 4shows an example interface400for configuring a child account. Example interface400includes the search fields302,304and306described relative toFIG. 3. The example interface400also includes an account summary307including the PIN field308, the PIN status drop-down310, and the balance field312. All described inFIG. 3. The account summary307also includes a parent PIN field402. As shown, the PIN field402displays the account number or PIN of the parent account for the selected child.

Example interface400also includes a move child PIN tab404. The move child PIN tab404includes a new parent PIN field406, into which the user may enter the account number or PIN of a new parent account to associate this child account to. The move child PIN tab404also includes a move button408that the user may activate to perform the move operation.

FIG. 5shows an example method500for enabling a parent-child account relationship. For clarity of presentation, the description that follows generally describes method500in the context ofFIG. 1. However, it will be understood that method500may be performed, for example, by any other suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware, as appropriate. For example, one or more of the database server, the client, or other computing device (not illustrated) can be used to execute method500and obtain any data from the memory of the client, the database server, or the other computing device (not illustrated).

At502, a child account associated with the parent account is identified, the parent account including a monetary amount, the child account being different than the parent account. In some implementations, identifying the child account includes querying a database to determine an associated parent account for a child account. In some cases, the monetary amount included in the parent account may be a dollar amount that has already been charged to the owner of the account, such as via credit card or other transaction. In some implementations, the monetary amount may be a prepaid monetary amount. The monetary amount may also be a credit limit.

At504, a communication associated with the child account is identified. In some implementations, the communication may be a telephone call placed between a subscriber and a destination. The communication may also be a conference call between multiple subscribers. The communication may also include a form of electronic communication, such as, for example, email, text or SMS, or any other suitable form of communication.

At506, at least portion of the monetary amount is transferred from the parent account to the child account after identifying the communication associated with the child account. In some implementations, transferring at least a portion of the monetary amount includes executing a database query to debit a balance associated with the parent account by a certain amount and credit the child the balance associated with the child account by the same amount. In some cases, a transaction record may be written to the database to indicate that this transfer has occurred.

In some implementations, the transfer at506may occur at multiple times during the duration of the communication, such as when the amount or time remaining on the child account falls below a threshold. In some cases, if the transfer at506is attempted and the parent account does not have sufficient funds for the transfer to occur, additional funds may be added to the parent account by charging an associated credit card, transferring funds from another account, or by any other suitable mechanism.

At508, the portion of the monetary amount in the child account is debited for charges associated with the communication. For example, if the communication is a telephone call associated with a rate of ten cents per minute, the monetary amount associated with the child account will be debited ten cents for every minute the communication continues.

At510, a remaining portion of the monetary amount is returned to the parent account from the child account when the communication ends. In some implementations, returning the remaining portion of the monetary amount to the parent account from the child account includes executing an SQL query against a database that debits the amount remaining on the child account by a certain amount and credits the amount remaining on the parent account by that same amount. In some cases, the entire monetary amount remaining on child account is returned to the parent account at the end of the indication. A portion of the monetary amount remaining on the child account may also be left on the child account when the communication ends. The amount that should be left on the child accounts when the communication ends may be configured based on the parent-child relationship.

In some implementations, the child account may include a nominal monetary amount when not associated with a communication. For example, the child account may be left with a monetary value of 2 cents after the communication ends and the remainder of the monetary amount is transferred back to the parent account.

In some cases, the parent account may be associated with a plurality of child accounts, and two or more of the child accounts associated with the parent may be used in communication simultaneously.

Purchase of an additional monetary amount may be initiated upon the monetary amount of the parent account reaching a value less than a threshold value. In some cases, initiating the purchase may include initiating a credit card transaction for a configured amount using stored credit card information associated with the parent account.

In some instances, the child account may be disassociated from the parent account, after which the child account may maintain a separate monetary amount from the parent account. The disassociation may be performed by updating a database table, such as by deleting a row specifying that the child account is associated with the parent account. In some cases, the child account may be used for communication after disassociation in a similar manner as it was used prior to disassociation, with a difference being that the child account will assess charges associated with the communication from its monetary amount and will not interact with the parent account. The disassociated child account will not receive a transfer of a monetary amount from the parent account at the beginning of the communication, and will not return an unused portion of the monetary amount to the parent account at the end of the communication.

In some cases, the parent account may be configured to be used in communications upon determination that the parent account is not associated with any child accounts. For example, an administrator may activate an option within an interface to enable the parent account to be used in communications, causing a database record associated with the parent account to be updated. After such configuration, a user may initiate a communication using the parent account in the same manner as any other account.

In some cases, it may be determined that the monetary amount in the child account is below a threshold, and an additional portion of the monetary amount from the parent account may be transferred to the child account upon determining that the monetary amount in the child account is below the threshold.

As previously discussed, the child account may be associated with configuration information separate from configuration information associated with the parent account, including, but not limited to, a speed dial configuration indicating phone numbers that may be dialed using a shortened series of digits, a language configuration indicating a language in which the account holder prefers to hear voice prompts, a billing configuration indicating how the child account will be charged for communications usage, or a branding configuration indicating branding messages to play during communications using the child account. The child account configuration information may also be separate from configuration information associated with other child accounts, such that each child account may have its own configuration information.

Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of wireline and/or wireless digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), a wide area network (WAN), Worldwide Interoperability for Microwave Access (WIMAX), a wireless local area network (WLAN) using, for example, 802.11 a/b/g/n and/or 802.20, all or a portion of the Internet, and/or any other communication system or systems at one or more locations. The network may communicate with, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and/or other suitable information between network addresses.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation and/or integration of various system modules and components in the implementations described above should not be understood as requiring such separation and/or integration in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Particular implementations of the subject matter have been described. Other implementations, alterations, and permutations of the described implementations are within the scope of the following claims as will be apparent to those skilled in the art. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results.