Managing user transportation needs without user intervention

A computer system comprising:

• a memory;
• one or more processing circuits communicatively coupled to the memory, wherein the one or more processing circuits are configured to:
• collect a first set of application data from a plurality of software applications on the device, wherein the plurality of software applications includes a clock application, a mobile payment application, and a texting application;
• detect a triggering event based on the first set of application data, wherein the triggering event corresponds to a state of the user, and wherein the state of the user is determined by comparing historical application data corresponding to one or more user-created triggering events to current application data to generate a probability of a transportation need, wherein the probability is based on at least a set of rules related to time, a set of rules related to event category, and a set of rules related to transportation needs, the probability meeting a threshold, and wherein the probability is first assigned according to a location parameter and subsequently adjusted according to a number of transportation needs for a plurality of users at the location parameter at a particular time;
• in response to the triggering event, determine the transportation need of the user based on the first set of application data without direct input from the user, wherein the transportation need includes both the particular time and the location parameter, and wherein the location parameter is located within a service area of a transportation provider;
• generate, based on both the particular time and the location parameter, a set of candidate transportation options for the user which satisfy the transportation need, wherein the candidate transportation options are ranked according to user preference, and wherein a first candidate transportation option includes walking and further includes a weather report, and wherein a second candidate transportation option includes public transportation and further includes a public transportation schedule;
• provide, to the user, a notification including the set of candidate transportation options;
• receive, from the user, a confirmation of one of the set of candidate transportation options;
• transmit, to the transportation provider, a requested transportation need for the user;
• detect a non-triggering event, based on a second set of application data collected from the clock application, the mobile payment application, and the texting application, wherein the second set of application data excludes one or more applications from the first set of application data, based on a determination that the one or more applications from the first set of application data do not affect the generation of the probability for the transportation need;
• compare the second set of application data to the first set of application data;
• in response to the comparison, determine the triggering event and the non-triggering event are similar;
• receive, from the user, confirmation that the triggering event and the non-triggering event are similar;
• re-define the non-triggering event as a second triggering event;
• and
• transmit, to the transportation provider, a second requested transportation need for the user.

A computer program product comprising a computer readable storage medium and computer program instructions that, when executed by a computer processor of a computer, cause the computer to:

• collect a first set of application data from a plurality of software applications, wherein the plurality of software applications includes a clock application, a mobile payment application, and a texting application;
• detect a triggering event based on the first set of application data, wherein the triggering event corresponds to a state of the user, and wherein the state of the user is determined by comparing historical application data corresponding to one or more user-created triggering events to current application data to generate a probability of a transportation need, wherein the probability is based on at least a set of rules related to time, a set of rules related to event category, and a set of rules related to transportation needs, the probability meeting a threshold, and wherein the probability is first assigned according to a location parameter and subsequently adjusted according to a number of transportation needs for a plurality of users at the location parameter at a particular time;
• in response to the triggering event, determine the transportation need of the user based on the first set of application data without direct input from the user, wherein the transportation need includes both the particular time and the location parameter, and wherein the location parameter is located within a service area of a transportation provider;
• generate, based on both the particular time and the location parameter, a set of candidate transportation options for the user which satisfy the transportation need, wherein the candidate transportation options are ranked according to user preference, and wherein a first candidate transportation option includes walking and further includes a weather report, and wherein a second candidate transportation option includes public transportation and further includes a public transportation schedule;
• provide, to the user, a notification including the set of candidate transportation options;
• receive, from the user, a confirmation of one of the set of candidate transportation options;
• transmit, to the transportation provider, a requested transportation need for the user;
• detect a non-triggering event, based on a second set of application data collected from the clock application, the mobile payment application, and the texting application, wherein the second set of application data excludes one or more applications from the first set of application data, based on a determination that the one or more applications from the first set of application data do not affect the generation of the probability for the transportation need;
• compare the second set of application data to the first set of application data;
• in response to the comparison, determine the triggering event and the non-triggering event are similar;
• receive, from the user, confirmation that the triggering event and the non-triggering event are similar;
• re-define the non-triggering event as a second triggering event;
• and
• transmit, to the transportation provider, a second requested transportation need for the user.